#807: request: move some session configuration into tg
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: enhancement | Status: new
Priority: normal | Milestone: 1.0
Component: TurboGears | Version: 0.9a5
Severity: normal | Resolution:
Keywords: |
--------------------------------+-------------------------------------------
Comment (by [EMAIL PROTECTED]):
ok. i made this patch that does the following:
* calls an automatic lock on cherrypy.session if
tg_session.automatic_lock is set ( i used the tg_session namespace as its
tg specific and not a cherrypy setting , as the rest of the options are )
* the file also now sets up a db connection for the session handling -
but only if its postgres. i couldn't find any connect info for sessions
in sqlite/mysql. i thought about putting it in model.py along with the
rest of the 'db' code, but then i realized that sessions could be not db
based ( like using a filstructure or memory ). something like this might
be better off where the config is parsed, and chained to support
post/mysql/files/and a user hook.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/807>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
