Django’s Cache Framework
Hi all, I thought this was interesting, and potentially relevant to Restlet and how it does caching. Ryan Tomayko linked to: http://docs.djangoproject.com/en/dev/topics/cache/ with the note: All frameworks should approach caching the way Django does. The core app/origin framework does no real caching but provides utility/helper methods for setting standard RFC 2616 cache related headers on the response easily and correctly. A completely separate set of caching goo ("middleware") sits between your app and performs the actual caching based purely on the headers set by the origin. The benefit to this approach is that caching is totally independent from the app framework and can be swapped out for a true gateway ("reverse proxy") cache at any time. here: http://tomayko.com/linkings/ (no direct link) -- Avi Flax » Lead Technologist » Partner » Arc90 » http://arc90.com
Re: Django’s Cache Framework
On Mon, Sep 15, 2008 at 11:40, Rob Heittman <[EMAIL PROTECTED]> wrote: > I agree! > Want to tack that reference on to > http://restlet.tigris.org/issues/show_bug.cgi?id=25 ? Cool, done!
Re: Django’s Cache Framework
I agree! Want to tack that reference on to http://restlet.tigris.org/issues/show_bug.cgi?id=25 ? - R On Mon, Sep 15, 2008 at 11:36 AM, Avi Flax <[EMAIL PROTECTED]> wrote: > The core > app/origin framework does no real caching but provides utility/helper > methods for setting standard RFC 2616 cache related headers on the > response easily and correctly.