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.
I keep seeing comments by various people suggesting that they don't
really understand how mod_wsgi works. I'd either like to understand
what the issue with SOPs is, or if it is a misunderstanding about how
mod_wsgi works, then correct that misunderstanding.
Thanks.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@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-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
