Hi, We initially define the timeout within the Session object's constructor. On the transactions which needs the user to be "off" a while (like document editing within FCKEditor) we update the user's session timeout in the page constructor. Following your tip on the session store I had a look on the code handling the session object we get to update the timeout. When a users logs in, we create a "MasterController" object that holds the session object. This way, the session object is always accessed through the "MasterController.session()" method, I'll look in this direction..
Thanks Fred Le 3 févr. 2010 à 23:36, Timo Hoepfner a écrit : > Hi Frédéric, > > random thought: AFAIK the timeout you set on the session object is only > considered when the session gets checked into the session store again, so as > long the session isn't checked in again (at the end of the RR-Loop), the new > timeout is not yet applied. When/where do you set the new timeout? > > Timo > > Am 03.02.2010 um 14:41 schrieb Frédéric JECKER: > >> >> Hi Timo, >> >> The fact is that disconnections are not happening during long transactions >> (we are using WOLongResponsePages for those) but after >> user inactivity. >> >> Regards >> >> Le 3 févr. 2010 à 11:56, Timo Hoepfner a écrit : >> >>> When those transactions are blocking the instance, the browser request >>> might be redirected to another instance by wotaskd. And that instance >>> doesn't know about the session and thus reports "session timed out" while >>> the correct message would be "session not found" in this case. Maybe this >>> is the case? Then use something like WOLongResponsePage or ERXLongResponse >>> to pevent the instance from blocking. >>> >>> Timo >>> >>> >>> Am 03.02.2010 um 11:13 schrieb Frédéric JECKER: >>> >>>> Hi, >>>> >>>> In our application's Session object we set the default session timeout to >>>> 3600 seconds by a call to the setTimeOut() function within the constructor. >>>> One some specific transactions we lengthen this time by modifying the >>>> user's session (again using the setTimeOut() function). >>>> We have very hazardous issues with those timeouts as sometimes users are >>>> experiencing session loss after only 10 minutes of inactivity. >>>> What are we doing wrong ? are there some good practices regarding timeout >>>> usages ? >>>> >>>> Thanks for your help >>>> Regards >>>> Fred >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list ([email protected]) >>>> Help/Unsubscribe/Update your Subscription: >>>> http://lists.apple.com/mailman/options/webobjects-dev/th-dev%40onlinehome.de >>>> >>>> This email sent to [email protected] >>> >> > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
