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
