On 8/27/08, Gustavo Narea <[EMAIL PROTECTED]> wrote: > Hello, everyone. > > I'm afraid tg.ext.repoze.who only supports the repoze.who SQL/form plugin(s), > and thus I'd like to know if we can make it support more so-called > identifier, > metadata and authentifier plugins under the same API? Better yet, why not > support all of the repoze.who plugins? This would make TG both scale up and > scale down in authentication. >
+1 on this Gustavo. Has you've already said, this would implie a project rename (which is fine by me). If you look a the code you'll see that the authentication layer (repoze.who) is already quite separated from the authorization layer (even though there are some bad coupling involved still). I'm 100% with you to start from scratch to separate the authorize decorator we have at the moment and to be able to switch authentication backend using conf files... The only point is that we would need to have this quite rapidly to avoid delaying Mark in his release cycle for TG2. At the same time this will allow us to remove the "tg.ext" namespace that causes trouble. I'd propose you get commit access to the tgtools repository and create a new project just for that so that we can work together on this. See: http://code.google.com/p/tgtools/ Florent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
