Lisa Dusseault wrote:

> One problem is that popular clients and servers only do exclusive locks, 
> so current practice is not sufficient to answer the unanswered questions 
> in RFC2518.  We could cut shared locks from WebDAV, require that only 
> one resource's lock may be updated by a LOCK refresh request, and that 
> would codify existing practice.  I believe that works even for 
> collection locks since a collection lock may not overlap another 
> exclusive lock.  So the new requirements would be something like:
>  - The LOCK refresh request MUST address the resource that was locked 
> (the root of the lock)


>  - The If header on the LOCK refresh request MUST contain one (and only 
> one) lock token, the token for the lock that is to be refreshed

I'd say it's harmless if it contains more lock tokens. The server can 
figure out which one actually identifies a lock on the request resource.

>  - The server MUST reject the request if the request-URI and token do 
> not match


Seems that we agree except for the minor point above; in practice I 
don't think that clients *will* submit multiple lock tokens in a refresh 
request, so this shouldn't be an issue.

Best regards, Julian

<green/>bytes GmbH -- -- tel:+492512807760

Received on Wednesday, 2 June 2004 11:34:38 UTC