Apache Mod-Python - Resolved: (MODPYTHON-111) Sessions don't set accessed time

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > April 2006 > Resolved: (MODPYTHON-111) Sessions don't set accessed time





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Resolved: (MODPYTHON-111) Sessions don't set accessed time
Graham Dumpleton (JIRA)

2006-04-02, 6:57 pm

[ http://issues.apache.org/jira/brows...ON-111?page=all ]

Graham Dumpleton resolved MODPYTHON-111:
----------------------------------------

Fix Version: 3.3
Resolution: Fixed

Autosave not implemented as described, but documentation updated to add additional note about need to save session to avoid timeout occuring.

> 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: documentation, session
> Versions: 3.1.4
> Environment: Suse 10, Apache2 worker
> Reporter: Sebastjan Trepca
> Assignee: Graham Dumpleton
> Fix For: 3.3


>
> 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/...ary/019889.html


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com