On Tuesday November 25, 2008 20:55:15 Dalius Dobravolskas wrote: > E.g. similar patches or similarly named cookies while they should be > different. I have accidentally named my AuthKit cookie and beaker > session the same name once and have had time until I have understood > where is problem. I have not checked that but I doubt that there is > any mechanism preventing user from doing such simple mistakes in > repoze.who. Or am I wrong?
Yes, you are wrong, as Gael pointed in the previous message. Come on, there's no such a problem with repoze.who. Based on the your statements on this thread, I'd say you barely read the repoze.who documentation. > > In all honesty, I don't like that approach of loading middleware just to > > add authentication methods. > > And instead you do the *same* just in slightly different way. > repoze.who specifies in config which plugins to load. AuthKit > specifies in config which middlewares to load. I offer to specify in > code which middlewares to load. Technically I can write AuthKit-like > middleware that allows to do the same as AuthKit (but I don't see > value in that). As I have already written repoze.who adds another > level of complication (components) to WSGI. > > > 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. > > It looks like you are the person who understands something here. Could > you explain to me why this division into components is good? Why is it > not enough WSGI for this task? Whatever you say. This is turning into an endless debate with the same arguments on both sides -- you vs. everybody else. -- 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 -~----------~----~----~----~------~----~------~--~---
