You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mod_python-dev@quetz.apache.org by "Graham Dumpleton (JIRA)" <ji...@apache.org> on 2007/04/05 13:34:32 UTC

[jira] Closed: (MODPYTHON-111) Sessions don't set accessed time on read

     [ https://issues.apache.org/jira/browse/MODPYTHON-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Graham Dumpleton closed MODPYTHON-111.
--------------------------------------


> Sessions don't set accessed time on read
> ----------------------------------------
>
>                 Key: MODPYTHON-111
>                 URL: https://issues.apache.org/jira/browse/MODPYTHON-111
>             Project: mod_python
>          Issue Type: Bug
>          Components: documentation, session
>    Affects Versions: 3.1.4
>         Environment: Suse 10, Apache2 worker
>            Reporter: Sebastjan Trepca
>         Assigned To: 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/mod_python/2006-January/019889.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.