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

AW: Are you using lock discovery?

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Wed, 27 Jun 2001 09:57:51 +0200
To: "WebDAV WG" <w3c-dist-auth@w3.org>
Message-ID: <NDBBKJABLJNMLJELONBKGEJJCOAA.stefan.eissing@greenbytes.de>
> [mailto:w3c-dist-auth-request@w3.org]Im Auftrag von Jason Crawford
> <<
> As I recall, the DAV Explorer client
> <http://www.ics.uci.edu/~webdav/> uses
> lock discovery. I believe it's smart enough to do lock discovery if a
> resource is locked, and DAV Explorer doesn't have the lock token. It then
> tries the lock token on the off chance the requesting principal actually
> owns the lock.
> >>
> Just a tangent...
> I'm sure Jim know this, but I'd just like to warn other client developers
> that servers are not obligated to expose the lock-token in the
> lock-discovery property.   Servers might chose not to expose the tokens so
> as to avoid the situation described in section 7.6.  Make sure
> your clients
> can handle a server not returning the lock token in the lock-discovery
> property.

Well, thanks for the warning. Which server(s) would that be? And will
they prevent a client application/operating system/network connection
from crashing or will they have another method to discover locks and
unlock resources?

Received on Wednesday, 27 June 2001 04:55:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:23 UTC