Proposal for meeting to consider..

I propose that apart from the no-cache indicators that all 
references to caching be removed from the HTTP 1.1 Spec.

There are many reasons why this proposal should be considered.

Caching is orthogonal to the rest of the protocol. It is optional and
if implemented should be transparent to the client/server (as should 
other objects such as proxies,gateways and tunnels using the 1.1 names)

In reality, caching is a necessary requirement to fix the demand problem
but should really be done outside HTTP.

An origin server does not know if a request/response is via a cache.

Responses are not entities. 

An entities owner is free to change their mind about the lifespan of an
object. So expiry and lifetime info can only be considered advisory at best.

Cached objects should NOT be considered persistant. All objects have a limited
lifetime in a cache. Cached objects not accessed in some timespan can be
thrown away. It is always safe to throw away data in a cache!

Pete.
ca
-- 
The TIS Network Security Products Group has moved!
voice: 301-527-9500 x123 fax: 301-527-0482
2277 Research Boulevard, 5th Floor, Rockville, MD 20850

Received on Tuesday, 23 January 1996 22:14:31 UTC