I've implemented repoze.who in one app so far. It was a bit difficult at first, but from my understanding is getting easier. I wrote a very simple tutorial at http://truefalsemaybe.com/2008/06/authorization-in-pylons-with-repozewho-part-1-htaccess/
I imagine I will write a followup soon, as I want to dive into some of the plugins mentioned above. Cheers, nym http://truefalsemaybe.com/ On Mon, Nov 24, 2008 at 1:06 PM, Domen Kožar <[EMAIL PROTECTED]> wrote: > > repoze.who has many plugins including recaptcha, openid, ldap. > also there is repoze.what on the way;) > > On 23 nov., 21:55, "Dalius Dobravolskas" > <[EMAIL PROTECTED]> wrote: >> Hi, >> >> >> What I need now is your opinion. Have I chosen the right path? What >> >> are you missing in my solution (both documentation and code)? >> >> Definetly there are some bugs/problems as well. >> >> > Why don't you use repose.who ? >> >> There are several reasons: >> >> 1) It is historical reason. If you search archive of this group you >> will find that I have implemented those middlewares at the same time >> as repoze.who. I just never documented it properly until now. >> >> 2) My first impression was and still is that repoze.who is alien to >> Pylons and/or WSGI. It just adds unnecessary layer of complexity to >> basically simple WSGI. That might be my inexperience, but nobody have >> explained me where is value until now. Just for example I have >> compares Form authentication. Result 140 (mine) vs. 220 (repoze.who) >> lines. Code does the same basically. Maybe if we will drop template >> code from repoze.who code we will get the same. The difference from my >> point of view: if you will use mine you just need to know WSGI, if you >> will use repoze.who you will need to learn repoze.who middleware (and >> it is not that small). >> >> 3) I have written OpenID authentication for Trac and OpenID >> authentication as WSGI middleware. I'm lazy enough not to write yet >> another plugin for repoze.who ;-) >> >> Technically I don't have anything against repoze.who. It is >> authentication middleware that does basically the same but under one >> umbrella (the same as AuthKit). If you are using repoze.who for form >> authentication already there is no reason why you should use mine form >> middleware. The final result will be the same. The only thing from >> authentication side in addition I offer is OpenID authentication ;-) >> >> From authorization side I offer some helpers functions (currently one >> function and decorator) that will help in authorization development >> and you can use that with repoze.who equally successfully if you want >> to. At least I don't see any reasons why you can't combine that. >> >> -- >> Daliushttp://blog.sandbox.lt > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
