On Apr 9, 7:00 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote: > D'oh, stupid me! I've pushed an update.
Thanks > Which comes back to my question yesterday, is it inefficient to call > session.save() several times in an action? If so, it's difficult to > have utility methods or library classes that modify the session. Like something that looks if the session have changed and do a save? Or have a save in __after__ base controller, but seems a bit inefficient on each request? > I'm planning to fill out the docstrings in the next few days. Yes, > the APIs have been changed, hopefully improved. But we've stuck close > to the original API unless there was a reason for changing. Sounds good to me. Blaise --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
