W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2008

Re: NEW ISSUE: Methods and Caching

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Tue, 18 Nov 2008 22:14:43 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1227042883.27155.138.camel@henriknordstrom.net>
On tis, 2008-11-18 at 10:40 -0800, Mark Nottingham wrote:

> 1) Major shared cache implementers interpret it this way (see Henrik's  
> mail, for example).
> 2) Allowing non-GET methods to be cacheable will IMO encourage the  
> development of GET-like extension methods. This will result in a lot  
> of data and metadata that isn't "on the Web" (i.e., you can't just  
> dereference a link to obtain it; now you need to know the correct  
> method as well).
> #1 may be a stronger reason to go this way as per our charter, but I  
> think in the long run #2 is a stronger motivation.

Yes. #2 is the important one imho.

In our implementation we actually do keep the method as an internal part
of the cache key, but that's for other reasons, and if I were to
reimplement the cache today the method would not be part of the key
getting rid of a lot of special cases..


Received on Tuesday, 18 November 2008 21:15:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:47 UTC