On 2/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> - the admin site is cached too, which makes it a bit hard to use.
> it might be a middleware ordering problem, but I haven't found a
> working combination. any ideas?
Ah, you must be using the per-site cache, right? I'm actually not sure
how the per-site cache would interact with the admin site -- the POSTs
would work, but the GETs would probably be cached. Is that what's
happening?
The best solution to this is to use per-view caches rather than the
per-site cache; that way, you have more fine-grained control over
which types of pages get cached.
> - I would like to explicitly remove pages from the cache, based
> on the URL. is there some public API for this that I haven't found ?
It's possible to interpret this question two ways, so I'll answer both:
* If you're wanting to physically delete a page from the cache, use
the low-level cache API:
from django.core.cache import cache
cache.set('views.decorators.cache.cache_page../some/url/.d41d8cd98f00b204e9800998ecf8427e',
None)
Note that the cache key contains "/some/url/", which is the URL that
you're wanting to remove from the cache, and the string
"d41d8cd98f00b204e9800998ecf8427e", which is a hash of "empty"
headers. That comes from django.utils.cache.get_cache_key(), which
looks at all the headers that should be considered with respect to
creating the cache key. "d41d8cd98f00b204e9800998ecf8427e" is the hash
for empty headers. Does this make sense? We should probably have a
simple helper function that clears the cache for a given URL, assuming
no headers.
* If you want to prevent a particular view from being cached (when
using site-wide cache middleware), there currently isn't a way to do
that. The tricky problem there is that it would cause a slight
performance decrease: Currently the cache middleware just looks at
each incoming URL, checks the cache for the URL with that key, and
returns the cached page if the key is found. If we were to allow
certain views to be left out of the cache, the cache middleware would
have to do URL dispatching to find out what the associated view is,
then check the view to see whether it should use the cache, then
finally check the cache. The extra overhead of URL dispatching isn't a
huge deal, but it's still kind of counter to caching. Thoughts on this
are welcome!
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
