Hi Fredrik, On Wed, 2006-03-01 at 07:57 +0000, [EMAIL PROTECTED] wrote: > anyone ? > > > however, there are two things that I haven't been able to sort > > out on my own: > > > > - 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?
Not going to touch this one; I'm not sure what is going on. > > - 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 ? Since you can control caching on a per-view-function basis, is it possible to set things up so that the URLs you do not wish to cache are served via a different view than the others (even if the view is just a wrapper around the common stuff)? If you can organise this, then using the @cache-control decorator can set the caching mechanism to "private", which should achieve what you want. This is documented in docs/cache.txt. However, maybe I am not understanding what you are asking, because you are saying "remove pages from the cache" (referring to the Django implementation?), whereas I am answering "how not to cache pages on an HTTP level" (referring to the result going out to the user). I am worried that your question is precise enough that I am not really answering what is being asked, so feel free to post more clues if you think that will help. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
