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.
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. Comments? Joseph P.S. Note that I haven't done anything with the login views yet (except to get logout working... kinda.) The new auth machinery bypasses the login forms since authentication happens before the login view is called. The views still probably need to do the cookie checks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
