[Systers-dev] Project Using Mailman Authentication

[Gloria W]

Hi Jaideep,
> Hi Malveeka,
>
> The MM 3.0 using the REST API's , the database that I am talking about is
> for storing the information of the user and considering the same with the
> usage of the REST API's to the same as we need to modify according to the
> Mailman 3.0 .
>
>
> ** It'll be great if you can tell us why you want to take this approach
> instead of using the Django framework
>    
As a Django geek who uses it daily and teaches it it, I would not 
recommend using it for this application. This web framework, although 
great for certain types of public facing web work, is comprised of a 
data model, authentication model, templating system and controller logic 
which are tightly bound, all the way down to the methodology. To 
force-fit all of the other decisions that come along with this tight 
binding, just to resolve one problem (authentication/authorization) is 
not a good decision, IMHO. If you only use one portion of Django, say, 
to accomplish authentication, you find yourself having to make 
concessions in your application design that you may regret later, while 
you hit Django limitations re: access to your session data, the request 
user data, and so forth.

I've seen people get very frustrated with Django two years after making 
such a decision for similar reasons. Some Python developers will tell 
you "Sure, it's easy to not use the db model, or not use the templating, 
and still use Django", and these developers usually have not actually 
tried this themselves. The theory sounds great but the practice turns 
out to be a maintenance horror over time. The point becomes, why use 
Django, if you're replacing/disabling pieces of it's core functionality, 
and breaking it's methodology? This is why there's CherryPy, Web.Py, 
Pylons, and so forth.

There are many needs and many tools, each tool has a methodology, a 
paradigm, and a resolution for a problem set. It is advisable to pick 
the tool that has a paradigm which is only bound to the problem you are 
trying to resolve. There are many Python standalone apps which only deal 
with authentication and authorization. Django is not one of them. Django 
has a great authentication model in the context of it's own web 
framework, but outside of it, it is difficult to use as a standalone 
authentication tool.

> *The code can be merged with the django framework as the code is written
> keeping MM 3.0 in mind.
>
> There is django based REST API interface which will be used most probably
> but we want to modify according to our needs ,  and django based open id
> auth[1] is also one of the option .
>    
Both web.py and cherrypy both have better ReSTful APIs, and were 
designed specifically to be HTTP based ReSTful engines. web.py has a 
slight advantage: it is easier to build URL factories in it than in 
cherrypy. cherrypy requies that all URL method pre-exist, and web-py 
does not, meaning that you can construct some very nice, dynamic, 
temporary URLs which expire. You can do the same in CherryPy, but it's 
sloppier, and takes more parsing work to determine what is happening 
when a message is received.

Some tell me Pylons really beats them all re: the ReSTful paradigm, but 
I haven't used it yet, so I cannot comment on this statement.

Gloria

> Thank You
>
>
> Regards
> Jaideep
>
> [0] http://code.google.com/p/django-rest-interface/
> [1] http://code.google.com/p/django-openid-auth/issues/list
>
>
> To unsubscribe from this conversation, send email to<systers-dev+mentor+unsubscribe at systers.org>  or visit<http://systers.org/mailman/options/systers-dev?override=67&preference=0>
> To contribute to this conversation, use your mailer's reply-all or reply-group command or send your message to systers-dev+mentor at systers.org
> To start a new conversation, send email to<systers-dev+new at systers.org>
> To unsubscribe entirely from systers-dev, send email to<systers-dev-request at systers.org>  with subject unsubscribe.
>
>