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

Re: [Bug 23] lock discovery vs shared locks

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Sat, 29 Oct 2005 08:42:34 -0700
Message-Id: <8eaf9241d62055518696cf3f434114e1@osafoundation.org>
Cc: w3c-dist-auth@w3.org
To: Julian Reschke <julian.reschke@gmx.de>


On Oct 29, 2005, at 6:15 AM, Julian Reschke wrote:

> Clarifying one thing on second read:
>
> Lisa Dusseault wrote:
>> ...
>> There were some comments in a previous email from Julian about how 
>> the lock token might not appear in the 'lockdiscovery' property if 
>> there are multiple (shared) locks on the resource. This statement 
>> doesn't fit my
>
> No, what I said (or meant to say is) that looking at DAV:lockdiscovery 
> in general will not help you at all, because it may contain *multiple* 
> entries (Geoff correctly pointed out later that it may not be there at 
> all).
>
> The only *reliable* way to find out the lock token a LOCK request 
> created is to look at the "Lock-Token" response header. This is the 
> only method that will always work, so please let's not waste time 
> confusing people by talking about other methods that may or may not 
> work.
>
Ok, I understand now why the lockdiscovery property is unreliable for 
this purpose.  But what about the body of the LOCK response (in 
addition to the Lock-Token header)?

Lisa
Received on Saturday, 29 October 2005 15:42:47 GMT

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