W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

Re: DAV:lockdiscovery on a checked-out resource

From: Jim Amsden <jamsden@us.ibm.com>
Date: Thu, 22 Mar 2001 17:41:37 -0500
To: ietf-dav-versioning@w3.org
Message-ID: <OF81F190FD.0A2AFF9E-ON85256A17.007BF60B@raleigh.ibm.com>
If UserA does a CHECKOUT, the resource won't be locked, it will just be 
checked out. PROPFIND on DAV:lockdiscovery won't show any locks to anyone. 
Now UserB doesn't know anything about versioning. If UserB just looks for 
locks and upon not finding any assumes the resource is writable, the write 
will fail because the resource is already checked out. LOCK will also fail 
for the same reason, it tries to do an implicit checkout. We assume that 
versioning unaware clients are not DAV unaware. That is, they can use 
PROPFIND and look at properties, including properties that indicate 
something is checked out. Its actually the user that's interperting this 
information, not the client. The client doesn't have to support any 
versioning specific protocol to access these properties. Although such 
clients make their users do extra work.

I guess I wasn't too clear...

UserA performs a CHECKOUT on a VCR.
UserB performs a PROPFIND of DAV:lockdiscovery to determine if the 
is "locked" (since the client is versioning unaware, ie only a class 2 DAV

What will DAV:lockdiscovery be?

If UserB's client is unaware of the DAV:checked-out property, then how 
they know it is "locked"?

Received on Thursday, 22 March 2001 17:42:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC