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

2006-04-01 Thread Graham Dumpleton (JIRA)
 [ 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] Assigned: (MODPYTHON-111) Sessions don't set accessed time on read

2006-03-05 Thread Jim Gallacher (JIRA)
 [ 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