> I agree with Diez here. > if repoze.what's goal is to be framework agnostic then this type of > thing should be inside repoze.what. That way if you are using pylons > or TG or whatever you will have one true way across frameworks. if we > start adding small things at the framework level it's going to be a > problem. > > For example with pylons there is no auth in the core so where is this > supposed to land? where will the require and the current_* methods be > in pylons? I'm thinking they will end up on a wiki and/or doc page > where you will be required to copy into your project. > > 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. Pylons is the only framework that elides this stuff, and is thus the only framework that requires SOP. So while it's already a necessary evil for Pylons, it shouldn't need to become a necessary evil for every framework (or anti-framework, like Werkzeug) that uses repoze.what. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
