[MODPYTHON-111] Sessions don't set accessed time on read

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.4
• Fix Version/s: 3.3.1
• Component/s: documentation, session
• Environment: Suse 10, Apache2 worker
• Assignee: Graham Phillip Dumpleton
• Reporter: Sebastjan Trepca
• Created: 22/Jan/06 05:45
• Updated: 05/Apr/07 11:33
• Resolved: 02/Apr/06 13:39

Description

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