On Wednesday 09 July 2008 16:16:04 chrism wrote: > I'll offer the following here as a general rule, lest anyone get the > wrong idea: it's better to write and use a new repoze.who plugin for > some specific purpose than it is to attempt to write the "one set of > plugins to rule them all". As a result, I'd guide folks towards > ditching any given existing plugin and implementing one that does > exactly what they need when their needs aren't serviced by the plugins > implemented in e.g. tg.ext.repoze.who. > > Independently, there is also a declarative way to configure repoze.who > via a config file, as opposed to making folks configure who "by hand" > in Python code. It probably makes sense for TG2 to use this to do > repoze.who configuration. See "Middleware Configuration via Config > File" in > http://repoze.org/viewcvs/repoze.who/trunk/README.txt?rev=1059&view=markup
By now, I'm also beginning to think that this would be better. I think TG2 customization should be more along the lines of e.g. login_handler_urls and such. Thanks for all the clarifications! Next stop: prefixing a TG-application with a given path & fix serving static content in that case :) Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
