On Jun 28, 7:18 am, "Shannon -jj Behrens" <[EMAIL PROTECTED]> wrote:
> * Use one action to put something into the session and then another
> to make use of the session. It's a work flow.
I've always thought that Pylons should have something that does that.
ie:
instead of being a beaker object, middleware sets up an object that
wraps beaker
class session:
__type= none
def __init__:
if config[] == live:
self.__type= beaker
else
self.__type= object
def __getattr__:
def __setattr__:
get/save to beaker/object
def save:
beaker.save()
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
