Add cache control (ETag, Last Modified) to django.contrib.syndication

[jerf@…]

Because RSS feeds can be the hardest hit part of a website, they need to be as efficient as possible; they are often the "inner loop" of a website. Good support for being able to return 304 with as little cost as possible is necessary, preferably as easily as possible.

[jerf@…]

a code only prototype of the cache system, for discussion purposes

[jerf@…]

Hang on, my impression of this is that it was rejected by discussion on the list.

If it is something that Django wishes to add, I think I've got a slightly better patch locally, I'm happy to write docs, and I'll burn it in on my own site before submitting it (since now the only thing to shoot for is 1.0, which I presume is a ways off). But I don't want to put any work on it if it's just going to be rejected.

[Malcolm Tredinnick]

The intention of your changes is correct, that was never rejected -- allowing early bailout is a worthy goal. I'm not sure your patch is doing the work in the right place, but it's probably pretty close. Attach your best patch so that we can review it and either apply it or do something similar.

[Ben Firshman]

Can't this be done with Django's existing caching tools now feeds are views?

​http://docs.djangoproject.com/en/1.2/topics/cache/

[Julian Bez]

ConditionalGetMiddleware should do the work of responding with 304 etc. so that's not needed here.

#7936 also is specifically about the Last-Modified issue and has a nice patch for it.

[Aymeric Augustin]

Django now provides general-purpose caching features that cover the scope of this ticket.

Use ​the condition decorator on your feed views: my_feed_view = condition(etag_func=..., last_modified_func=...)(MyFeedClass())