Hello, Jorge. On Tuesday November 25, 2008 17:11:24 Jorge Vargas wrote: > 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.
I don't think so. As I explained in the previous email, it's such a trivial functionality (if implemented at the application/framework level; this is, if you have the environ at hand) that I think there will be no difference from one implementation to another. > 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. The other issue is that I'm not sure it fits in repoze.what; we're talking about identity stuff. Keep in mind that repoze.who deals with identification and authentication (who are you?), while repoze.what deals with authorization (what can you do?). repoze.what provides a simple repoze.who metadata provider which is the one that loads the groups and permissions into repoze.who's identity dict. I think that providing information about the current user is out of the scope of an authorization framework, even if such data was loaded by the authorization framework itself. But again, I think we definitely need a function that returns the whole identity. Cheers. -- Gustavo Narea <http://gustavonarea.net/>. Get rid of unethical constraints! Get freedomware: http://www.getgnulinux.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
