Re: MultiAuthMiddleware vs AuthMiddleware

2006-03-05 Thread Gary
Gary wrote: > I also agree that the new home should be down a level, but again > disagree with the 'auth' abbreviation. Perhaps django.authen? Actually, I like the "everything should be an app" thinking. And if that is the case, all apps should go in one directory (seems to be /django/contrib).

Re: MultiAuthMiddleware vs AuthMiddleware

2006-03-05 Thread Gary
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 tha

Re: MultiAuthMiddleware vs AuthMiddleware

2006-03-03 Thread Joseph Kocherhans
On 3/3/06, Linicks <[EMAIL PROTECTED]> wrote: > > I think that it's important to have a default authentication system > similar to the current one. Agreed. I didn't mean to suggest that MultiAuthMiddleware would require any more configuration or work differently out of the box than Django does cu

Re: MultiAuthMiddleware vs AuthMiddleware

2006-03-03 Thread Linicks
"""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 d

MultiAuthMiddleware vs AuthMiddleware

2006-03-03 Thread Joseph Kocherhans
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 djan