Re: Witango-Talk: application vars timing out

[Peter Ternström]

Im almost through replacing all references from application to a custom 
scope. So far no problems, but it is still only on our development servers. 
Well see how it goes on the production server.

Thanks again for all good input!
Peter
----- Original Message ----- 
From: "Dory" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 12, 2004 5:36 PM
Subject: Re: Witango-Talk: application vars timing out


Absolutely I have, and it does not allow me to set either
variabletimeout or variabletimeouttrigger for the application scope.
From my original post:
When I try this I get this error, "You may not set the configuration 
variable
(variabletimeouttrigger) in the (application) scope".
and if I try to set variabletimeout, I get "You may not set the
configuration variable
(variabletimeou) in the (application) scope".
I expect they are not allowed to be set because they are not supposed
to timeout in the first place.
Peter, does this work for you?
On Thu, 11 Nov 2004 08:22:56 -0700, Ben Johansen <[EMAIL PROTECTED]> wrote:

Have you tried this?
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=application VALUE=0>


Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Witango Developement
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf