the timeoutTrigger is set in user scope and determines what app is triggered when the user scope times out.  For instance:

<@ASSIGN user$variabletimeouttrigger value="http://<@domain>/taf/cleanup.taf?<@USERREFERENCEARGUMENT>">

can be used to launch the cleanup task that purges all the rows in a table relating to this user's visit. 

using this to create application variables doesn't make sense unless you want to do something to those variables as a consequence of the user's variables expiring. 

If you want to set/clean up app scope variables, then you should put a test in the beginning of your logic that looks for the application variables and if they don't exist, sets them.



On Aug 16, 2006, at 12:40 PM, John Michelin wrote:

You may not set the configuration variable (variableTimeoutTrigger) in the (application) scope.

Consult the documentation for a list of valid scopes that can be used with this variable.

I receive this message after trying to set the variableTimeoutTrigger in a class file that sets up/resets the application variables. Am I missing something?

 

John Michelin

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to