Re: Middlewares disable for specific views

2010-04-06 Thread Tim Shaffer
It's actually the auth context processor that queries for messages,
not the auth middleware.

The TEMPLATE_CONTEXT_PROCESSORS are only processed when you using
RequestContext. So there are numerous ways to get prevent the auth
context processor from being used. You could just not use
RequestContext for that specific view. Or you could create a custom
auth context processor that doesn't query for messages and use that.


On Apr 6, 6:32 am, Thierry  wrote:
> Is it possible to disable a middleware such as the authentication one
> for specific views where they are not needed?
> The constant querying for messages annoys me a bit :)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.



Middlewares disable for specific views

2010-04-06 Thread Thierry
Is it possible to disable a middleware such as the authentication one
for specific views where they are not needed?
The constant querying for messages annoys me a bit :)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.