W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: Summary of ETag related issues in RFC2518bis

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 20 Dec 2005 09:06:07 +0100
Message-ID: <43A7BB6F.9020409@gmx.de>
To: Jim Whitehead <ejw@soe.ucsc.edu>
CC: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>, WebDav WG <w3c-dist-auth@w3.org>

Jim Whitehead wrote:
> 
> If I'm a client that has an exclusive write lock, then if I PUT to that 
> resource, the stored entity should not be modified by anyone other than 
> the server. In this case, which is the most common one for DAV-based 
> editing, it's still very useful for the client to receive the final etag 
> value in the response to PUT. Why? It saves the client from having to 
> poll an uncertain number of times before it receives the final, stable 
> etag value.

Well. If the client has the lock, why would it need the ETag in the 
first place?

 > ...

Best regards, Julian
Received on Tuesday, 20 December 2005 08:07:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:12 GMT