Graham Dumpleton wrote: > > > On Jul 9, 6:22 am, "Mike Orr" <[EMAIL PROTECTED]> wrote: >> Having one SOP, pylons.app, containing all the Pylons globals has long >> been suggested by me. The value could also be attached to the >> controller instance -- one attribute instead of several. That would >> be for users who object to getting request info from a module global, >> and because I've heard there are some situations (somemod_wsgi >> applications?) that can't use the SOPs. > > Not understand what SOPs are all about, can you explain why they would > be a problem in mod_wsgi.
The StackedObjectProxy -- it's a proxy facade over objects, like the request, registered in a thread-local manner. I don't really see why mod_wsgi would care. In non-threaded situations the stacking still comes into play -- that is, you can register new requests that overlap the old requests, then pop them off the stack. But again, it shouldn't matter to mod_wsgi at all. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
