Re: Summary of ETag related issues in RFC2518bis

On Tue, 20 Dec 2005, Jim Luther wrote:

>
> On Dec 20, 2005, at 8:58 AM, Stefan Eissing wrote:
>> Mathematically speaking if PUT(x) is the function in the server that takes 
>> the client input and modifies it, so that a subsequent GET(PUT(x)) defines 
>> the content a client gets back. We are talking about the situation where x 
>> != GET(PUT(x)) because the other case is trivial.
>
> As the implementer of a WebDAV file system client, the whole idea of x != 
> GET(PUT(x)) makes my head hurt. For file systems to work, they require x == 
> GET(PUT(x)) if there have been no PUTs from other clients between the PUT and 
> the GET.

Well, as long as it is carefully hidden by the server, the client should 
care at all if there is a discrepancy between the edited document and 
what's on the server. You can have the same issue with caching.

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."

Received on Tuesday, 20 December 2005 17:29:42 UTC