I would rather we not go ahead with adding req.get_session() at
this time. At least not how it was envisaged to be done previously.
I'll come back with a bit of analysis after I review where we were
up to previously.
Graham
On 12/03/2006, at 8:47 AM, Jim Gallacher (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MODPYTHON-59?page=all ]
Jim Gallacher reassigned MODPYTHON-59:
--------------------------------------
Assign To: Jim Gallacher
Add get_session() method to request object
------------------------------------------
Key: MODPYTHON-59
URL: http://issues.apache.org/jira/browse/MODPYTHON-59
Project: mod_python
Type: New Feature
Components: session
Versions: 3.1.4, 3.1.3, 3.2.7
Environment: All
Reporter: Jim Gallacher
Assignee: Jim Gallacher
Fix For: 3.3
Attachments: Session.py.diff.txt
Users will get session instances by calling req.get_session(). If a
session already exists it will be returned, otherwise a new session
instance will be created. Session configuration will be handled using
apache directives rather than within their code.
Using this scheme means only one session instance will be created per
request, which will eliminate the deadlock problems many people
experience. Also, using this scheme makes it possible for sessions to
be properly handled within psp pages and across
req.internal_redirect() calls.
Code will be commited to svn shortly.
--
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
