The variabletimeout is relevant to the scope applied: Request: n/a - all variables are lost on the completion of the request User: time since last hit on any user variable per user scope key Domain: time since last hit on any domain variable per domain scope key Application: time since last hit on any Application variable per application scope key Custom: time since last hit on any Custom variable per custom scope key System: never timeout
In other words, system$variabletimeout (the setting in the .ini) always applies unless the variabletimeout in the relevant scope it set differently such as: <@ASSIGN user$variabletimeout 60> allows user variables (FOR THIS USER ONLY) to expire after an hour of inactivity. Robert -----Original Message----- From: Bryan Hughes [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 3:38 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Error Files From what I gather... Application scope variable, if set in .ini files do not time out. The variabletimeout setting I'm pretty sure is for USER scoped variables. On Nov 11, 2003, at 3:19 PM, Jan Magnusson wrote: > Bryan, > > I don't have any answer to your problem, but was wondering if you > happend to > know how the application scope variables behave/time out. > > Depending on where in the documentation I read I seem to get somewhat > different results: > > - Programmers Guide, page 349: Application scope variables do NOT > timeout. > - PG, page 484, variableTimeout: according to this application scope > variable timeout could be set. I tried it, but it doesn't work > generating > a -609 (Cookie scope ???) error. > - PG; page 392: according to the alphabetical list variable timeout > can not > be set. > > - In reality though it seems to me the application scope variables time > out/are purged by the server with the last user leaving or timing out > from > the application (my guess). At least they are gone and have to be > reassigned... > > Thankful for any light to be shed on this. > > Jan > >> -----Original Message----- >> From: Bryan Hughes [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, November 11, 2003 21:32 >> To: [EMAIL PROTECTED] >> Subject: Re: Witango-Talk: Error Files >> >> >> Any one have any input on my Witango Application problem? >> >> >> On Nov 9, 2003, at 8:59 PM, Bryan Hughes wrote: >> >>> Okay, so far I've set up my ini files. >>> >>> ****** domains.ini ****** >>> [Domains] >>> NewDom=This is my test domain >>> >>> [NewDom] >>> 1=www.newdom.com >>> 2=192.168.0.3 >>> >>> >>> *****applications.ini***** >>> [Applications] >>> Default= >>> NewDomApp=My new domain application for the root level >>> >>> [Default] >>> PATH=/ >>> >>> [NewDomApp] >>> DOMAIN=NewDom >>> PATH=/ >>> DEFAULTERRORFILE=C:\\errors\\error.taf >>> >>> My error.taf just has a results page that spits out "This is the >>> error >>> page". >>> >>> So I set up a taf in the root of NewDom and do a <@CALC EXPR="1/0">. >>> This returns the normal error and not "This is the error page". >>> >>> Then I replaced the Calc with <@DOMAIN> and <@APPNAME>. >>> >>> I get NewDom and Default. >>> >>> For some reason it's not seeing the application as part of the >>> NewDomApp but of the Default Application because they have the same >>> path ( / ). >>> >>> How do I give applications the same path on different domains? >>> >>> >>> >>> >>> On Nov 9, 2003, at 8:28 PM, Bryan Hughes wrote: >>> >>>> Stephen, >>>> >>>> This supposedly can be done with your "domain" and "applications" >>>> initiations. >>>> >>>> In these files you may set up different domains and subdirectories >>>> of >>>> domains (applications) and specify each with their own unique >>>> configuration settings, one of which being defaultErrorFile. These >>>> settings on affect the domain and path specified. >>>> >>>> I've tried setting this up before and had never got it going after >>>> following the directions in the Witango documentation. >>>> >>>> I am currently trying it this evening for a domain. I'll report back >>>> my success/failure. >>>> >>>> -B >>>> >>>> >>>> On Nov 8, 2003, at 6:19 PM, Stephen Su wrote: >>>> >>>>> Anyone? >>>>> >>>>> I was trying to setup different master, default error files for the >>>>> different websites sitting on the same server? Does anyone know the >>>>> most effective way to do this? I had assigned a >>>>> "Application$defaultErrorFile" var in each of the root directories >>>>> but no luck. Is there something else I have to do or other files >>>>> that I have to delete or alter on the server? Is there a better >>>>> way? >>>>> >>>>> Thank you all ahead of time and I hope everyone is having a nice >>>>> weekend, >>>>> Stephen >>>>> >>>>> ___________________________________________________________________ >>>>> __ >>>>> ___ >>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf >>>> >>>> ____________________________________________________________________ >>>> __ >>>> __ >>>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf >>> >>> _____________________________________________________________________ >>> __ >>> _ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf >> >> ______________________________________________________________________ >> __ >> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf >> > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
