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

mod_python

Sessions don't set accessed time on read

Created: 22/Jan/06 05:45 AM Updated: 05/Apr/07 11:33 AM

Return to search

Component/s:

documentation, session

Affects Version/s:

3.1.4

Fix Version/s:

3.3.1

Time Tracking:

Not Specified

Environment:

Suse 10, Apache2 worker

Resolution Date:

02/Apr/06 01:39 PM

Description

« Hide

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

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Sebastjan Trepca made changes - 14/Feb/06 09:33 PM

Field	Original Value	New Value
Component/s		documentation [ 11609 ]

Jim Gallacher made changes - 06/Mar/06 08:20 AM

Assignee

Jim Gallacher [ jgallacher ]

Graham Dumpleton made changes - 02/Apr/06 01:36 PM

Assignee

Jim Gallacher [ jgallacher ]

Graham Dumpleton [ grahamd ]

Graham Dumpleton made changes - 02/Apr/06 01:36 PM

Status

Open [ 1 ]

In Progress [ 3 ]

Graham Dumpleton made changes - 02/Apr/06 01:39 PM

Status	In Progress [ 3 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]
Fix Version/s		3.3 [ 12310101 ]

Graham Dumpleton made changes - 05/Apr/07 11:33 AM

Status

Resolved [ 5 ]

Closed [ 6 ]