On Mon, Jul 14, 2008 at 10:12 AM, alex finn <[EMAIL PROTECTED]> wrote: > Can anybody explain me why django's AuthenticationMiddleware is > setting user attribute of request.__class__ and not of request itself? > What's the point of setting it on a class level rather then on the > instance level?
Because it's not setting the user directly, it's setting a LazyUser object, which is a Python descriptor. Descriptors only work the way they're supposed to if they're set at the class level. Using a descriptor allows it to go through the trouble of getting the user only when it's actually gonna be used, and also cache it for later, so it doesn't have to go through all that extra work more than once per request, no matter how many times the user is accessed. If you're interested in learning more about descriptors, I've written a couple blog posts about it that might help. http://gulopine.gamemusic.org/2007/nov/23/python-descriptors-part-1-of-2/ http://gulopine.gamemusic.org/2007/nov/24/python-descriptors-part-2-of-2/ -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
