On Sun, Nov 2, 2008 at 8:57 AM, bo <[EMAIL PROTECTED]> wrote: > Yes, that may be true. > > But why does the 'default' behavior impose these dependencies when > they are not required? As that context processor has this other 'side > effect' of making an entire site "Vary" under a cookie, hit the > session and hit the DB.
I think you're confused - the context processor doesn't set a cookie, so it isn't causing any Vary behavior, and admin *does* currently depend on it - it needs the info the processor provides. Unless admin was rewritten to add them to context manually on every view, it will continue to need it. > and one would need to override every other function that calls > "template.RequestContext' which is most of the meat of sites.py. Uh, no you wouldn't - if you tell admin not to check for that context processor, you could replace the auth processor with a custom one that only works in admin's path and as such wouldn't add any db hits to the rest of the site. So if your goal is to make only admin do the queries for that data, it's entirely possible. -- Collin Grady --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
