Joseph Kocherhans wrote: > 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.
And the reason for creating an AuthMiddleware would be to simply do what Django does now, but without the added overhead of MultiAuthMiddleware? Caching of some kind (model, session, etc.) would certainly help with the overhead. Like now, caching could be done in the session by default as sessions already have configurable expiration times, preventing stale credentials. Ideally, I think there shouldn't be both a MultiAuthMiddleware and an AuthMiddleware; there should only be an AuthMiddleware. I also have some grief with the ambiguity of the 'Auth' abbreviation, does it stand for authentication or authorization? We might soon be wanting some MultiAuth(orization)Middleware as well. > Also, the stuff in django.parts should move to django.contrib.auth and > django.parts should die. > > 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. I can't agree enough that everything authentication-related should be in one place. This includes: /django/contrib/auth/ /django/parts/auth/ /django/views/auth/ /django/views/decorators/auth.py and even the request.user stuff in: /django/core/handlers/modpython.py /django/core/handlers/wsgi.py I also agree that the new home should be down a level, but again disagree with the 'auth' abbreviation. Perhaps django.authen? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
