[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=comments#action_12366331 ]
Sebastjan Trepca commented on MODPYTHON-111: -------------------------------------------- OK, I understand and agree with your but then someone should change the documentation because now it says: " A session will timeout if it has not been accessed for more than timeout, which defaults to 30 minutes. An attempt to load an expired session will result in a ``new'' session. " >From this line I thought accessing the session means that I execute the load() >method, but I was apparantly wrong and spent few hours debugging my >application and then few hours more for debugging mod_python. Can someone then please edit that line in docs and be more explicit about what that "accessing" means so people won't be confused when session will suddenly expire? > Sessions don't set accessed time on read > ---------------------------------------- > > Key: MODPYTHON-111 > URL: http://issues.apache.org/jira/browse/MODPYTHON-111 > Project: mod_python > Type: Bug > Components: session > Versions: 3.1.4 > Environment: Suse 10, Apache2 worker > Reporter: Sebastjan Trepca > > When you read or access session it does not set new accessed time so it > eventually dies(depends on the timeout). > It only sets the accessed time when you save the session and that is not how > sessions normally function(at least not on all other systems). IMHO it should > set its accessed time when it was actually accessed and not only when saved. > A bit more about this issue can be found here: > http://www.modpython.org/pipermail/mod_python/2006-January/019889.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
