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 

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:
For more information on JIRA, see:

Reply via email to