On Tuesday November 25, 2008 12:29:17 Dalius Dobravolskas wrote: > > What if you need to combine multiple authentication schemes in the same > > site? > > You can add multiple middlewares. The problem is when middlewares or > plugins conflict with each other (e.g. because of lack of options). > repoze.who does not help to solve this problem.
Can you please provide one example in which that problem is present in repoze.who? Just one. In all honesty, I don't like that approach of loading middleware just to add authentication methods. repoze.who's approach is elegant because it has broken up the various components involved in authentication (the so-called identifiers, authenticators, challengers and metadata providers) so that they can all work _harmoniously_, controlled by repoze.who itself. That's why repoze.who scales up and scales down. Cheers. -- Gustavo Narea. General Secretary. GNU/Linux Matters <http://gnulinuxmatters.org/>. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
