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 "Sebastjan Trep?a (JIRA)" <ji...@apache.org> on 2006/01/21 21:46:44 UTC
[jira] Created: (MODPYTHON-111) Sessions don't set accessed time on
read
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 Trep?a
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
[jira] Commented: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Jim Gallacher (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=comments#action_12366333 ]
Jim Gallacher commented on MODPYTHON-111:
-----------------------------------------
I'll update the documentation.
> 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
>
> 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
[jira] Closed: (MODPYTHON-111) Sessions don't set accessed time on
read
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-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/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
[jira] Assigned: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=all ]
Graham Dumpleton reassigned MODPYTHON-111:
------------------------------------------
Assign To: Graham Dumpleton (was: Jim Gallacher)
> 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
>
> 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
[jira] Commented: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Sebastjan Trepca (JIRA)" <ji...@apache.org>.
[ 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.
"
[jira] Assigned: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Jim Gallacher (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=all ]
Jim Gallacher reassigned MODPYTHON-111:
---------------------------------------
Assign To: Jim Gallacher
> 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: Jim Gallacher
>
> 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
[jira] Work started: (MODPYTHON-111) Sessions don't set accessed
time on read
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=all ]
Work on MODPYTHON-111 started by Graham Dumpleton
> 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
>
> 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
[jira] Commented: (MODPYTHON-111) Sessions don't set accessed time
on read
Posted by "Graham Dumpleton (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=comments#action_12363542 ]
Graham Dumpleton commented on MODPYTHON-111:
--------------------------------------------
Note that making such a change could have noticeable consequences as far as performance goes. Where login based session authentication is used to cover access to everything in a directory, including auxiliary files such as static images included in a HTML page, you would incur the override of a commit on every single access, including to the images. In those situations it is preferable that only the page/code with represents the core resource should perform the commit for time accessed. The only way you can achieve this is to leave it as now and for the programmer to code the commit explicitly in the required place. If you auto commit on every access, you impose the performance hit on everyone and doubly so for existing code which already performs the required commit. Thus changing this may have a significant impact on existing code.
BTW, a lot of those other systems probably came along after mod_python implemented sessions. They also do what they do as part of a bigger picture of making it easier for dumb users to use the systems. An aim of mod_python on the over hand is performance, control and flexibility. By auto commiting, you have taken away just a little bit of that control as once done you can't revert the change. It is thus perferable that if you want auto commit, you implement it in a layer above the API that is provided. Since a good design would implement session creation in a web application in one spot, it means you only have to accomodate for it in one spot, so in practice it should not be a big drama for a user to do themselves.
> 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 Trep?a
>
> 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
[jira] Updated: (MODPYTHON-111) Sessions don't set accessed time on
read
Posted by "Sebastjan Trepca (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MODPYTHON-111?page=all ]
Sebastjan Trepca updated MODPYTHON-111:
---------------------------------------
Component: documentation
> 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
>
> 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