Sorry I should've added that this feature wasn't working properly in pre-5.5.006 versions in my post.
I'm glad to see that Witango now handles the USR automatically. That makes a lot of sense, and really makes this feature easy to use, as well as useful. Robert -----Original Message----- From: Customer Support [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 16, 2005 11:50 PM To: witango-talk@witango.com Subject: Re: Witango-Talk: VariableTimeoutTrigger This is fixed in the next 5.5 release. What happens in 5.5.003 and earlier is that by the time the thread that has fired the trigger tries to get the variable store another idle thread has kick in and purged the user variables. The trigger more often than not misses the variable store by a few milliseconds on a server with light traffic. The busier the server the more likely that the variables were available when the trigger was running. With the new trigger mechanism you do not need to send the user reference in the URL. The witango server will now manage that for you automatically in the http header it sends. Witango Support On 17/03/2005, at 3:30 PM, Bill Conlon wrote: > This is a bug, which I've reported to Witango. Phil tells me it will > be fixed in the next 5.5 release. I posted a test case on the list > last November. > > > On Wednesday, March 16, 2005, at 07:22 PM, Roland Dumas wrote: > >> Well, it triggers the URL, but the user variables are disappeared. >> >> >> On 3/16/05 6:33 PM, "Robert Shubert" <[EMAIL PROTECTED]> wrote: >> >>> Yup. Only you need a full URL as if you are using a cron entry and >>> you >>> have to (I believe it's mandatory) have the USR argument. Thus: >>> >>> <@ASSIGN user$variabletimeouttrigger >>> "http://www.site.com/path/logout_user.taf?<@USERREFERENCEARGUMENT>"> >>> >>> Robert >>> >>> >>> -----Original Message----- >>> From: Roland Dumas [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, March 16, 2005 9:20 PM >>> To: witango-talk@witango.com >>> Subject: Witango-Talk: VariableTimeoutTrigger >>> >>> Just trying to understand how this works. >>> >>> If I set <@ASSIGN user$variabletimeouttrigger >>> value="/taf/mytimeouttaf.taf"> >>> >>> Then as session variable expires, this taf is triggered as though the >>> user >>> were hitting it, with all the user's variables available? >>> >>> >> >> >> ______________________________________________________________________ >> __ >> 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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
