Re: Summary of ETag related issues in RFC2518bis

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 UTC