#8698: Middleware Documentation still refers to CacheMiddleware
------------------------------------+---------------------------------------
Reporter: anonymous | Owner: nobody
Status: reopened | Milestone: 1.0
Component: Documentation | Version: SVN
Resolution: | Keywords: middleware, cache
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* status: closed => reopened
* resolution: worksforme =>
Comment:
This isn't a good default strategy. You can still use `CacheMiddleware` is
it's working for you now or you really know what you're doing. It's far
safer to use the split version, though, since it means you can safely add
other middleware later without having to hurt your brain trying to work
out if it's something that will affect the cache key. It's an omission in
the middleware docs, in any case, since these two middleware pieces exist.
--
Ticket URL: <http://code.djangoproject.com/ticket/8698#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
