| Graham Dumpleton (JIRA) 2005-07-23, 7:45 am |
| [ http://issues.apache.org/jira/brows...action_12316577 ]
Graham Dumpleton commented on MODPYTHON-59:
-------------------------------------------
I previously commented on this on the mailing list but can't find the
email to reference.
The issue I raised was along the line that in order for this scheme to
be able to work nicely in with other code which creates and manages
session object, there probably also needs to be a way to determine if
the session object has already been created and to explicitly set the
sesssion, thereby bypassing the get_session() method. Ie., I don't
necessarily believe it should just be a black box whose behaviour
can't be overridden.
At minimum, it still should be possible to access the session object as
req.session and set it by assigning to req.session. Working code set
for 3.2 still doesn't appear to allow this.
Wish I could find the email as I may have suggested better reasons
in it. :-(
> 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: core
> Versions: 3.2.0
> Environment: All
> Reporter: Jim Gallacher
>
> 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
|