W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2004

Re: Call for consensus on UNLOCK Request-URI being lock root

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 30 Jun 2004 20:37:54 +0200
Message-ID: <40E30882.2040603@gmx.de>
To: Lisa Dusseault <lisa@osafoundation.org>
Cc: WebDAV <nnw3c-dist-auth___at___w3.org@smallcue.com>

Lisa Dusseault wrote:

> Yes, I read these today, but it was my interpretation that this testing  
> applied to the UNLOCK request.  What about LOCK request to refresh a  
> lock?  Does that also work on resources other than the lock root?  I  
> think servers would probably implement them the same way, but I was  
> curious whether you'd tested it explicitly.

Sorry. Related to this is 
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/0191.html>, 
but that is about URLs in tagged "If" headers (where I found that 
servers do not seem to care).

Right now I'm saying...

"4.2.3.1 DAV:locks-refreshed postcondition

Timers associated with the those locks submitted in the "If" request 
header whose lock root is the resource identified by the Request-URI 
MUST be reset to their original value (or alternatively to the new value 
given in the "Timeout" request header)."

..basically because it seems nobody asked that question before. 
Assuming we'd find out that servers do not care for LOCK/refresh either, 
would we want to relax the spec text?

Best regards, Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 30 June 2004 14:38:22 GMT

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