- From: Jeffrey Mogul <mogul@pa.dec.com>
- Date: Thu, 28 Dec 95 14:59:03 PST
- To: koen@win.tue.nl (Koen Holtman)
- Cc: http-caching@pa.dec.com
I would have no problem with a protocol that allows caches to contain
both a) and b) types of responses. Allowing b) would mean the
introduction of a new Cache-Control directive
"response-same" "=" delta-seconds
(we can argue about the name later) that would allow the server to
express that it will produce exactly the same entity body for that
request for at least N seconds (some particular response headers
headers, like Date and Cache-control, could change during that time
though).
This is not the only possible approach. I've started to write
up my proposed design in detail, so perhaps I should wait to explain
it further.
> So I would ask people not to treat the "caching model" implicit
>in any existing HTTP 1.x draft as a given.
OK. I do feel however that we need to take the "caching model"
implicit in the 1.1 draft as a starting point of our model.
Would someone like to define what this is? I'm happy to include
this as one of the design alternatives, but it's pointless to
treat it as an alternative as long as there is no explicit description.
I most certainly do not believe we can treat it as both implicit
and sacred at the same time.
-Jeff
Received on Thursday, 28 December 1995 23:02:19 UTC