Mike Chambers wrote: > I just did some local debugging, and notice something interesting. The > cache key appears to be generated based on a hash of the request headers. > > This means that visiting the same page in two different browsers will > generate 2 unique keys, which means that the cache isnt used. > > For example, on my site, loading /about/ > > Here are the cache keys generated: > > Firefox > views.decorators.cache.cache_page../about/.d08052b9800d6ec1d568dc223a1312f3 > > Safari > views.decorators.cache.cache_page../about/.d41d8cd98f00b204e9800998ecf8427e > > So, if i visit the page first in Firefox, the page will be dynamically > generated. If I then visit the page in Safari, the page will once again > by dynamically generated (and not pulled from the cache). > > If I am understanding this correctly, then it has a couple of implication: > > 1. it will be very difficult, if not impossible to remove a specific > path / page from the cahche > > 2. cacheing isnt that efficient since it is per-page / per headers, and > not just per page. > > Anyone have any input on this? I realize that there is a good chance > that I am missing something obvious.
http://www.djangoproject.com/documentation/cache/#using-vary-headers http://www.djangoproject.com/documentation/cache/#the-low-level-cache-api -- Norman J. Harman Jr. Senior Web Specialist, Austin American-Statesman ___________________________________________________________________________ You've got fun! Check out Austin360.com for all the entertainment info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
