Hi, I'm trying to escape the zope monster and so I started to play with Pylons as a possible solution. I find its simplicity really appealing and, in general, I like it a lot.
However, I'm having a bit of a problem with the paradigm shift and need some guidance. I am planning to build an app. which consists of a number of business objects in a hierarchy. This hierarchy provides info and context which users can explore in a stateful-manner. If I have understood Pylons correctly, each http request will effectively result in my object hierarchy being set up and then torn down, with all the overhead this entails. What I think I want is to set up a user session, during which the object hierarchy persists. When the session is closed, hierarchy is torn down. During the session, any data changes are reflected in the model¦database. What is the Pylons way to do this? any pointers as to how I should go about it? I only need an outline, I can probably rtfm to get the details. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
