Re: EDITS for Section 13.20 (Cache Replacement for Varying Resources)

>>   13.20 Caching Responses
>>
>    If a new cacheable response (see sections 10.7.2, 13.11.2, 13.11.3
>>and 13.14) 
>    is received from a non-varying resource while an old response for the
> same 
>    resource is cached, the cache SHOULD insert the new response into
> cache storage 
>    (see section 13.7.3).

Not accurate -- the cache never needs to do any such thing in order to
remain conditionally compliant with HTTP (the meaning of "SHOULD").

>>   If a new cacheable response is received from a varying
>    resource with a certain variant-ID while an old response with the
> same
>>   variant-ID for the same resource is cached, the cache SHOULD insert
> the new
>    response into cache storage.
> 
>    The cache SHOULD now use the new response to reply to this request
> and to any
>    future requests that would previously have caused the old response to
> be 
>    returned.
> 
> 	Note: In some cases, this may mean that the cache chooses to delete the
> old
>>	response from cache storage to recover space.
>>
>    Note: The above mechanism will not trigger deletion from cache
>>storage of old
>>   responses with variant-IDs that will no longer be used.  It is
>>expected
>>   that the normal 'least recently used' update heuristics employed by
>>   caches will eventually cause such old responses to be deleted.

That's all just meaningless baggage.  Why do you want to add it?
What problem are you trying to solve?

As far as I can tell, this section (13.20) does not belong in the spec,
no matter how many times it is rewritten.


 ...Roy T. Fielding
    Department of Information & Computer Science    (fielding@ics.uci.edu)
    University of California, Irvine, CA 92717-3425    fax:+1(714)824-4056
    http://www.ics.uci.edu/~fielding/

Received on Thursday, 2 May 1996 02:31:51 UTC