#8698: Middleware Documentation still refers to CacheMiddleware
------------------------------------+---------------------------------------
Reporter: anonymous | Owner: nobody
Status: closed | Milestone: 1.0
Component: Documentation | Version: SVN
Resolution: worksforme | Keywords: middleware, cache
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by ubernostrum):
* status: new => closed
* needs_better_patch: => 0
* resolution: => worksforme
* needs_tests: => 0
* needs_docs: => 0
Comment:
Most people can still use `CacheMiddleware`, and `CacheMiddleware` still
exists; it's just in certain situations -- as described in the caching
docs -- that you need to use the separate bits to avoid problems.
--
Ticket URL: <http://code.djangoproject.com/ticket/8698#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
