> While I understand Ken's point about the book, in that it is no longer
> the complete reference, I would *not* recommend just forgetting it.
> Instead, use it as the valuable resource it is, and supplement your
> nautical sojourn with reference to the online documentation as needed.
>  I, for one, have found the book to be extremely helpful overall, as
> well as useful in helping to clarify parts of the online documentation
> that are, perhaps, overly terse.


I agree ! After trying to configure the django cache system  I notice that
the online docs are wrong and the django book have the correct information
about the order of  MIDDLEWARE_CLASSES.

ONLINE DOCS YOU WILL FIND:

If you use CacheMiddleware, it's important to put it in the right place
within the MIDDLEWARE_CLASSES setting, because the cache middleware needs to
know which headers by which to vary the cache storage. Middleware always
adds something to the Vary response header when it can.

Put the CacheMiddleware  *before*  any other middleware that might add
something to the Vary header (response middleware is applied in reverse
order).

DJANGO BOOK YOU WILL FIND THE CORRECT INFORMATION

If you use CacheMiddleware, it's important to put it in the right place
within the MIDDLEWARE_CLASSES setting, because the cache middleware needs to
know the headers by which to vary the cache storage.

Put the CacheMiddleware ***after*** any middlewares that might add something
to the Vary header.

As you can see the djangobooks can help sometimes ;-)

Regards,

Marcelo Sanches




--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to