Just as a vote of confidence, I pondered the same today two things today! Why are there no official docs for session in the pylons docs ( nor indeed the cookbook) and why not call session.save() in a try/finally in your base controller __call__() (altho that would it would probably be more like if session['user']: session.save() to avoid saving every random user)
On Tue, Apr 8, 2008 at 9:33 PM, Mike Orr <[EMAIL PROTECTED]> wrote: > > Session handling seems to be missing in the Pylons Official Docs. My > particular question is, when should session.save() be called? For > instance, I have an action that calls a few utility methods that all > modify the session, and a generic Flash class that also modifies the > session. Should I call session.save() in all of them, or is that > inefficient? One issue is that the user of the Flash class shouldn't > have to know whether/how the session is being used. Should I just > call session.save() once at the end of the action? Or in the base > controller? > > -- > Mike Orr <[EMAIL PROTECTED]> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
