Are any of you using ETags with Django? I'm wondering what the easiest solution for determining whether I need to send back a 304 is. I have last-modified timestamps on my models, so I could conceivably query those and match them against the If-Modified-Since header. It seems like I'd be doing two queries, though. Once for the latest timestamp and again for the real objects.
The other alternative seems to be to create a model specifically for determining whether result sets have been dirtied or not. I'd have to make sure my update routines updated this object whenever a model got updated that would dirty a result set. Although new content will be added (hopefully) frequently, I'm not sure there will be that much changing once it's been added. I definitely want to reorder the list of content based on weighting a random ordering, so for some views it will be difficult to rely on ETags for caching. Since Django encourages the use of clean urls, though, it seems like I should be able to use ETags with my models, especially when getting the detail for a particular instance. How would I attack this in a reasonably clean (i.e. able to be reused with any views I want ETags for...but not *every* view) way? I'd like hear how others have solved this before I spend a lot of time hitting dead ends. Thanks! Jon Brisbin http://jbrisbin.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?hl=en -~----------~----~----~----~------~----~------~--~---
