- From: Yves Lafon <ylafon@w3.org>
- Date: Wed, 21 Dec 2005 11:11:33 +0100 (MET)
- To: Ted Hardie <hardie@qualcomm.com>
- cc: Julian Reschke <julian.reschke@gmx.de>, Jim Whitehead <ejw@soe.ucsc.edu>, Cullen Jennings <fluffy@cisco.com>, WebDav <w3c-dist-auth@w3.org>
On Mon, 19 Dec 2005, Ted Hardie wrote: > At 12:09 AM +0100 12/20/05, Yves Lafon wrote: >> >> >> My implementation returns the ETag that asubsequent GET would see, so >> option (2). Ans I am in the case where the PUT entity and the served >> entity will not be the same, as there are CVS actions done during the >> PUT, so possible keyword extensions, etc... > > Are these property changes, or changes to the entity itself? If to the > entity, how does a get-range work? To the entity itself, a GET-range based on what has been PUT will obiouvsly fail (but it can fail for many other reason, like going through a proxy cache that goes offline between the PUT and the GET and serv stale content). -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Wednesday, 21 December 2005 10:12:11 UTC