> you could host a pretty busy site with 10 concurent witango threads. True, and I have had busy sites with version 5.0 (and previously T2K). However, after upgrading the site with 5.5 I run out of 10 concurrent userrefs pretty quickly (since I assume a userref is concurrent until it times out or users vars are purged). What I am finding is that as soon as the 10 userrefs are reached, the 11th userref causes a license exceeded error to be recorded in the event log and the server coming to a stop (meaning we need to restart the service to get it going again). This is seriously disrupting.
> From: John McGowan <[EMAIL PROTECTED]> > Reply-To: <[EMAIL PROTECTED]> > Date: Fri, 22 Oct 2004 15:12:48 -0500 > To: <[EMAIL PROTECTED]> > Subject: Re: Witango-Talk: RE: problem with quote value and 5.5 server > > As far as i know, the small business server has always had a limitation > on the number of user sessions. not threads... > > you could host a pretty busy site with 10 concurent witango threads. > > /John > > Trevor Green wrote: > >> I am still experiencing this problem and can reproduce it easily. I >> created a test taf and sent a detailed bug report to With. I do not >> expect to see a response (as the web site says there will be no >> response to bugs reported). >> >> On another note, I have now noticed that the small business server >> version 5.5 is limited to 10 concurrent users (i.e. 10 concurrent >> userrefs), which is now another problem for me with 5.5. I always >> though it was unlimited users but limited in threads. If you check the >> witango website you will see that it is now limited to 10 concurrent >> users (maybe was like this before but I never have licensing issues >> before � which I have now). >> >> >> >> >> Tom, >> >> I don't have 5.5. up and running otherwise I would try to reproduce it >> too. >> >> /John >> >> Tom Storey wrote: >> >>> I've been watching the list for some response to this problem, but >>> have seen nothing. Is no one else having this problem and I'm just >>> missing something or is this a problem? I've emailed support, but I've >>> not received anything from them ether. >>> >>> >>> Tom Storey wrote: >>> >>>> Hi >>>> >>>> I'm having the quoting problem right now on 5.5. I've moved some of >>>> my programs that I was running on 5.0 to 5.5. Now all of the updates, >>>> that use text fields in my db, have to be quoted, in criteria box, >>>> before the update will work. I've made a small test .taf to test this >>>> and you can't use a <@var> in criteria box because if you quote it >>>> <@var> shows up not it's value. >>>> >>>> Tom >>>> >>>> John McGowan wrote: >>>> >>>>> noSQLEncoding should only affect the behavour of a directDBMS >>>>> action. An update action should not be affected. >>>>> >>>>> I've had to use the same method that Trevor mentions below and it >>>>> has always worked on 5.0. I've yet to upgrade to 5.5 so I can't >>>>> comment on whether or not it works for me, but now I'm worried about >>>>> it. >>>>> >>>>> Trevor, please raise this as a bug with Witango if you can easily >>>>> reproduce it. >>>>> >>>>> /John >>>>> >>>>> Ben Johansen wrote: >>>>> >>>>>> Can you explain why you need the quotes when it is a char field? >>>>>> >>>>>> Have you tried the noSQLEncoding switch >>>>>> >>>>>> Around the update action >>>>>> >>>>>> Ben >>>>>> >>>>>> >> ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> *From:* Trevor Green [mailto:[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]> >>>>>> *Sent:* Friday, October 15, 2004 6:20 PM >>>>>> *To:* [EMAIL PROTECTED] >>>>>> *Subject:* Witango-Talk: problem with quote value and 5.5 server >>>>>> >>>>>> I have a problem with 5.5 on Mac OSX server and MySql. I have an >>>>>> update action with a field which is has the Quote value attribute >>>>>> set to false. I am trying to update the field with the following >>>>>> expression >>>>>> >>>>>> <@ifempty <@arg ownership>>null<@else>'1'</@if> >>>>>> >>>>>> i.e. sql should read /field=null/ or /field=�1�/ depending on the >>>>>> value of ownership. This worked fine on 5.0 but since upgrading to >>>>>> 5.5 the server insists on quoting even when quote value is set to >>>>>> false. So, I either get a value of null (i.e. the word null being >>>>>> stored in the field � which is a char field) or the value �1� (i.e. >>>>>> quote 1 quote) instead of having an empty field or a field with the >>>>>> value of 1. Has anyone else experienced this? >>>>>> >>>>>> Trevor Green >>>>>> >> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
