"""RequestUserMiddleware is a horribly ugly name, and in the
latest diff
attatched to http://code.djangoproject.com/ticket/1428 I've renamed it
to MultiAuthMiddleware. I'm wondering if people think it would be
worthwhile to add something else called AuthMiddleware that would do
more or less what django does now. It would be the default when you
created a new project."""

I think that it's important to have a default authentication system
similar to the current one.  The easy to use and powerful built in
system made/makes Django very attractive to me.  As a newer user of
Django it helps to have as much consistency as possible.  In my mind it
makes sense to have all of the  authentication mechanisms as a
plugin/extension/etc. to the MultiAuthMiddleware.  You could have a
"default_auth" plugin/* that implements the current authentication
system by default.  If I wanted to switch to LDAP, NIS, or custom
mechanism I would just reconfigure the authentication back end.   I
hope I'm not missing the boat here :)

"""Also, the stuff in django.parts should move to
django.contrib.auth and
django.parts should die."""

This appers to be another place to help clarify the API to a new user.
The *.auth is more explicit to me than *.parts.  Parts could be
anything...


"""It might also make sense to move some of the machinery
(AuthUtil,
maybe others) down a level into a new django.auth package and/or to
put the multiauth stuff in a django.contrib.multiauth package."""


Once again, anything that can be done to provide a consistent and
explicit naming and location conventions would really help the learning
curve and usability.

I'm really looking forward to the new authentication system built
around multiple authentication mechanisms in mind.

    
Thanks for the hard work on this!

--Nick


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to