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: Fri, 18 Nov 2005 08:59:44 -0800
Message-Id: <e534eff36188a15f898293ccb91de7ad@osafoundation.org>
Cc: webdav WG <w3c-dist-auth@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>

This is great data Julian, very useful.

On Nov 18, 2005, at 8:52 AM, Julian Reschke wrote:

>
> Proposal:
>
> 1) Describe lock token discovery after successful LOCK in exactly one 
> place in the spec, and make sure examples are correct
>
> 2) Remove the requirement to return the <lockdiscovery>, and mention 
> that change in the "changes" section, including rational and suggest 
> servers continue to return it when backward-compatibility with older 
> clients is an issue.
>
What about clients learning the lock timeout?  I know some clients use 
the <lockdiscovery> in the response body to learn what timeout the 
server chose, and use that to know when to refresh the lock.

Lisa
Received on Friday, 18 November 2005 17:00:00 GMT

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