On 12/18/07, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > I hadn't thought of any of this before, but I really like the concept. > It seems to me that `context` is certainly better than `c` but you > are right that it doesn't really convey the fact that its essentially > request local state. My personal preference, after hearing your ideas, > would be: > > pylons.c -> pylons.request.state > pylons.session -> pylons.request.session > pylons.g -> pylons.request.app_globals
I don't see how this is better than 'pylons.app_globals' and so on. Unless...right: the "stupid user" won't be able to do "dirty trick" like "from pylons.request import app_globals" since pylons.request is some weird thing and not a python module. Er? And while we're on a "house cleaning" topic, I had read somewhere that "globals (singletons) are a design smell". If that's true what was the point of making request and response "globals"??? I must be seeing all this in a different light, so sorry for sarcasm. I don't like "changes for the sake of changes" and I don't like "we know better than the user" either. Max. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
