To do what you describe you can use the variable "VARIABLETIMEOUTTRIGGER"
remember to have it in user scope though.... VARIABLETIMEOUTTRIGGER Just before a user's, application's, domain's or a custom scope's variables expire, the HTTP URL specified in that scope's variableTimeoutTrigger is activated. (The time after which variables expire is set in the configuration variable variableTimeout.) This URL could be used to execute an application file that clears the database of temporary user session data, purges the user name from a list of logged-in chat users, or many other possibilities. There is no default timeout trigger. To have a trigger execute upon the expiry of each user's variables, you would assign the desired value to variableTimeoutTrigger (in user scope) at some point during each user's session. To set a trigger for a particular domain, you would assign to variableTimeoutTrigger in domain scope in an application file being accessed from that domain. To set a trigger for a particular application, you would assign to variableTimeoutTrigger in application scope in an application file being accessed from that Witango application. The URL in this configuration variable cannot contain meta tags because the trigger mechanism does not evaluate meta tags. Nevertheless, you can include user-, application-, or domain-specific information in the URL by including meta tags in the assignment to variableTimeoutTrigger, which are evaluated at the time of the assignment. --- Dan Stein <[EMAIL PROTECTED]> wrote: > 15 > > I was just looking at that thinking it might be an > issue and also wondering > if somehow I could use the variable timeout trigger > to clear user variables > for those many many people who probably never log > out. > > If I could trigger the logout.taf it would clear > them out. > > Dan > > > -- > Dan Stein > Digital Software Solutions > 799 Evergreen Circle > Telford PA 18969 > Land: 215-799-0192 > Mobile: 610-256-2843 > Fax 413-410-9682 > FMP, WiTango, EDI,SQL 2000 > [EMAIL PROTECTED] > www.dss-db.com > > > > From: JJ Smith <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > Date: Mon, 3 Feb 2003 17:42:09 -0800 (PST) > > To: [EMAIL PROTECTED] > > Subject: Re: Witango-Talk: Help with opening day > disaster > > > > What is the system variable "THREADPOOLSIZE" in > > witango.ini set to... > > > > > > > > THREADPOOLSIZE > > > > This variable determines the number of worker > threads > > that the Witango Server allocates to process > requests. > > This is the maximum number of requests that > Witango > > Server tries to process simultaneously. If the > number > > of concurrent requests reaches this limit, > additional > > requests are queued until threads become > available. > > Increasing this number may have a detrimental > effect > > on hardware that cannot support the load. The > default > > value is 20. > > > > --- Dan Stein <[EMAIL PROTECTED]> wrote: > >> Re opened our site today to swim registration. > These > >> as rapid users who will > >> do anything to try and beat the system. For > instance > >> although we had the > >> site closed till 3PM we had 320 people hit it > trying > >> to get in even though > >> they new in advanced it was closed. And before I > >> removed the login taf > >> altogether had a half dozen people bypass the > start > >> page and go right to a > >> bookmarked login page. > >> > >> So it was no surprise when at 3PM we opened it we > >> had almost immediately 140 > >> user all on at the same time. > >> > >> In the 1st 10 minutes seems lots of stuff was > >> strange. The user variables > >> were getting lost for some people but not all. > Even > >> had two out of 234 > >> invoices get multiple users entered in the line > >> items. > >> > >> I looked through the code and don't see where > this > >> could be happening. I did > >> trap more places for the reg_iD the main variable > >> being present. > >> > >> I had to shut it down and have a dozen emails > from > >> people who are angry. > >> > >> It does look like many of these people were from > AOL > >> but I am using > >> everything known to humankind to defeat proxy > >> servers so I don't see that it > >> should be a problem. > >> > >> Is there some setting in my server I need to > change. > >> Could it be maxing out > >> somehow under the load and that causing problems. > >> > >> I am pretty desperate to get this fixed. We > tested > >> the hell out of this > >> thing but could not test under this kind of load. > >> > >> I need to get this back up but I'm afraid to do > it > >> without an answer to the > >> problem. > >> > >> Server is running Windows 2000 Server latest > patches > >> SQL 2000 SP3 and > >> Witango 5 latest version. > >> > >> > >> > >> > >> > >> > >> -- > >> Dan Stein > >> Digital Software Solutions > >> 799 Evergreen Circle > >> Telford PA 18969 > >> Land: 215-799-0192 > >> Mobile: 610-256-2843 > >> Fax 413-410-9682 > >> FMP, WiTango, EDI,SQL 2000 > >> [EMAIL PROTECTED] > >> www.dss-db.com > >> > >> > >> > > > ________________________________________________________________________ > >> TO UNSUBSCRIBE: send a plain text/US ASCII email > to > >> [EMAIL PROTECTED] > >> with unsubscribe witango-talk in > the > >> message body > > > > > > __________________________________________________ > > Do you Yahoo!? > > Yahoo! Mail Plus - Powerful. Affordable. Sign up > now. > > http://mailplus.yahoo.com > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email > to [EMAIL PROTECTED] > > with unsubscribe witango-talk in the > message body > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] > with unsubscribe witango-talk in the > message body __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
