Next message: Geoffrey M. Clemm: "modeling RCS style branches with activities"
Message-Id: <3.0.5.32.20000625110516.02a81880@127.0.0.1>
Date: Sun, 25 Jun 2000 11:05:16 -0400
To: ietf-dav-versioning@w3.org
From: Joe Meadows <joe.meadows@boeing.com> (by way of "Ralph R. Swick" <swick@w3.org>)
Subject: [Moderator Action] draft-ietf-deltav-versioning-04.8
[caught in spam trap -rrs]
Date: Sun, 25 Jun 2000 02:51:36 -0400 (EDT)
Sender: meadowsj@boeing.com
Message-Id: <3955A846.315BC782@boeing.com>
Old-Date: Sat, 24 Jun 2000 23:35:50 -0700
From: Joe Meadows <joe.meadows@boeing.com>
To: ietf-dav-versioning@w3.org
The current draft appears to assume that compliant clients are talking
directly to compliant servers. However, some consideration may need to
be given to its use through either HTTP/1.1 or HTTP/1.0 proxies.
For instance, several of the methods provide responses that are not
supposed to be cached; i.e.
"A CHECKOUT response MUST NOT be cached."
It would probably be helpful to have examples that explicitly set
the appropriate HTTP headers to make sure that responses aren't cached
(i.e. by delta-V unaware proxies).
>>REQUEST
CHECKOUT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
>>RESPONSE
HTTP/1.1 200 Ok
Cache-Control: no-cache
Pragma: no-cache <--- maybe??
Location: http://www.webdav.org/ws/core/3/foo.html
I haven't been following this activity, so sorry if I've missed something
obvious.
Cheers,
Joe Meadows