Re: Caching question

On Fri, Jun 6, 2008 at 2:11 PM, Peter Rowell <[EMAIL PROTECTED]> wrote: > I'm a little confused. The docs (http://www.djangoproject.com/ > documentation/middleware/#django-middleware-cache-cachemiddleware) > say, and the code appears to support it, that if > django.middleware.cache.CacheMiddleware

Re: Caching question

@James: I'm a little confused. The docs (http://www.djangoproject.com/ documentation/middleware/#django-middleware-cache-cachemiddleware) say, and the code appears to support it, that if django.middleware.cache.CacheMiddleware in the MIDDLEWARE_CLASSES list, then caching is turned on for the whol

Re: Caching question

> * If you apply the cache_page decorator to a specific view, the > caching performed by that decorator only occurs for anonymous users. > * If you use the {% cache %} tag in a template, the caching occurs for > all users in all situations regardless of anonymous status. > * If you use the low-lev

Re: Caching question

On Thu, Jun 5, 2008 at 3:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I've read the caching documentation several times, but must be missing > some fine points. If I have > CACHE_MIDDLEWARE_ANONYMOUS_ONLY = True > set, does per-view or template fragment caching override that? If you have

Re: Caching question

On Jun 5, 6:22 pm, Peter Rowell <[EMAIL PROTECTED]> wrote: > > does per-view or template fragment caching override that? > > From looking at django/middleware/cache.py, I would say that the view > (and therefore the template) never get a chance to override. This > check is done early in the reques

Re: Caching question

> does per-view or template fragment caching override that? >From looking at django/middleware/cache.py, I would say that the view (and therefore the template) never get a chance to override. This check is done early in the request processing cycle, even before URL routing is performed. Peter