Re: Witango-Talk: variableTimeoutTrigger

[[EMAIL PROTECTED]]

Not sure, that you have read this in the online manual: variableTimeoutTrigger User, application, domain, and custom scopes 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 Tango 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. See also: mailDefaultFrom userAgent variableTimeout variableTimeout User, application, domain, custom, and system scopes The system scope version of this configuration variable determines the default period, in minutes, after which domain and user variables expire. For user variables, the expiry timer is reset to zero each time the user accesses Witango Server. For application variables, the expiry timer is reset each time the Witango application is accessed. For domain variables, the expiry timer is reset each time a user from the domain accesses Witango Server. For custom variables, the expiry timer is reset each time a variable in the custom scope is accessed. Setting variableTimeout to zero indicates that variables never expire. In general, this value is appropriate for the domain scope only. To change the expiry timeout period for domain variables only, assign the desired value to variableTimeout in domain scope. For example, to specify that "domain" scope variables never expire, make the following assignment: <@ASSIGN NAME=variableTimeout SCOPE=domain VALUE=0> Setting this variable with user scope sets the expiry timeout for the current user, overriding the value in the system scope. For example, to specify that a "User" scope variables expire in 15 Minutes, make the following assignment: <@ASSIGN NAME=variableTimeout SCOPE=User VALUE=15> Setting this variable with application scope sets the expiry timeout for Witango application, overriding the value in the system scope. Hope this have answer your question Regards Daniel   ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, July 20, 2003 5:41 PM Subject: Witango-Talk: variableTimeoutTrigger > Hi, > I am unable to find sufficient documentation/examples to use the Config Var > called "variableTimeoutTrigger" in my applications. > > Can someone explain what this variable does, with an example? The Tango > docmentation is not good enough. It does not tell the syntax, nor an example. > Help please. > > Thanks. > -TTT > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf