nevermind... i should have looked at the docs before sending this message...
after looking at the docs, i would have to say that perhaps the absense
of a value implies a zero value?
/John
John McGowan wrote:
As i understand it, the "System" regulates the expiration of
persistent variables...
System$variableTimeout sets the timeout for all persistent variables
handled by the server, (domain and user) all other domain scopes have
different rules about when things expire...
You can't set this variable, "per user" or "per domain" so a
Domain$variableTimeout wouldn't make sense...
/John
Scott Cadillac wrote:
Hi Folks,
I apologize that I'm not staying as up to date as some of you with
Witango programming, but could someone correct me if I’m wrong, but
shouldn't a VariableTimeout variable be automatically assigned to
each variable scope?
I have several sets of domain scope variables (in a multi-domain
system using a single set of TAF files), and I noticed that some of
the domain scopes don't have a VariableTimeout variable.
Shouldn't there automatically be one when any domain scope var is
assigned? Or have I totally lost my marbles?
The documentation doesn't explicitly say this, but is implied with
"The system scope version of this configuration variable determines
the default period, in minutes, after which domain and user variables
expire."
Running 5.5.009 Liquorice (Win32) on Windows 2003.
Calling @@Domain$variableTimeout returns an empty value, and is not
in the <@VARNAMES SCOPE=domain> list.
Thank you in advance.
Scott Cadillac, Email: [EMAIL PROTECTED] http://scott.cadillac.bz
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
--
John McGowan
[EMAIL PROTECTED]
P 847.608.6900 x 110
F 847.608.9501
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
