>> SOP is at the core of pylons but it allows you to do a lot of >> interesting stuff, so I say it's a necessary evil. > > My $.02: SOP is a hack that works around the fact that the environ > (and other request-local vars) are not passed around but are instead > kept as thread-locals.
>If you pass them around, it's unnecessary. And frankly, I like Ian bicking's suggestion that we keep request-specific information on the WebOb request object and if necessary put some "framework hooks" in that populate the extra values of request. Then there's just one thing that you have to pass around inside your framework, and you can easily achieve the "stacked" part just by keeping your request around even after you call some other WSGI app/middleware. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
