On Dec 18, 2007 6:30 PM, Mark Ramm <[EMAIL PROTECTED]> wrote: > > > pylons.c -> pylons.request.state > > pylons.session -> pylons.request.session > > pylons.g -> pylons.request.app_globals > > I don't think session belongs in request personally, isn't the whole > point of the session that it persists _across_ requests.
There's nothing wrong with putting everything in the request, including the response. It's information *for this request*. Whether some of the data persists beyond the request is no big deal, as long as users are reassured that certain things are guaranteed to be discarded (query params, scratch variables). -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
