Like Dan said, Witango has an Session expiry setting - look in the "t4server.ini" or "witango.ini" file.
All modern web-application environments have a similar timeout setting, based on the User's inactivity. When a Session timeouts, what happens is that the Server will purge the User variables and release them from memory (or whatever storage mechanism the environment uses), as well, the Session "key", "id" or "reference" is no longer tracked on the Server. So, even though a browser may still contain the Session "key" - the Server does not acknowledge it anymore. If your code initializes new User variables after an expired Session - some environments will re-use the old "key", or issue a new one. Understanding this behavior is important. Setting the expiry timeout too long can become a burden on the Server and slow it's performance - setting it too short can complicate the User experience. The long term storage of these User variables by the Server is an important factor in your program design. Meaning...make sure you explicitly "scope" all your variables when assigning and calling them - to prevent too many variables being loaded unnecessarily in memory, and for Witango to manage and track. If you don't need the variable after the execution of a TAF - then make sure they are assigned as "local" scope. You'll see much better performance. Prior to Witango v5, the default scope for variables not explicitly scoped was "user" - which I always felt was a mistake by the engineers. Starting in Witango v5, Phil did the right thing by setting the default to "request" (a.k.a. "local"). Sorry for the long-winded post, but sometime I can't help myself - something that always drove my ex-wife crazy :-> Hope it helps anyway. Cheers......... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- ----- Original Message ----- From: "Dan Stein" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 9:59 AM Subject: Re: Witango-Talk: Session Logout > The variable expiration time default is 30 minutes. You can change it but I > have found 30 works pretty good. > > All you need to do to enforce it is to check for some user variable that you > assign at log in on each page. > > > -- > Dan Stein > Digital Software Solutions > 799 Evergreen Circle > Telford PA 18969 > Land: 215-799-0192 > Mobile: 610-256-2843 > Fax 413-410-9682 > FMP, WiTango, EDI,SQL 2000 > [EMAIL PROTECTED] > www.dss-db.com > > > > From: Michael Dittbrenner <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > Date: Fri, 21 Mar 2003 10:50:05 -0500 > > To: <[EMAIL PROTECTED]> > > Subject: Witango-Talk: Session Logout > > > > Does Witango have a session logout so that after being idle for 5 mins or so > > the system will auto log you out of the session. If so can someone let me > > know the metatag and if you have any examples id greatly appreciate it. > > > > Michael Dittbrenner > > > > -- > > Educational Directories Unlimited, Inc. > > > > Michael Dittbrenner > > Programmer > > http://www.StudyAbroad.com > > http://www.GradSchools.com > > A service of EDU, Inc... http://www.EDUdirectories.com > > A partner of EDU Internet Strategies: http://www.EDUInternetStrategies.com/ > > > > [Phone] 610-499-9200 > > [Fax] 610-499-9205 > > [E-mail] [EMAIL PROTECTED] or [EMAIL PROTECTED] > > > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
