You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2004/12/13 15:50:41 UTC
dav locking/property question
Hey Julian (and others):
I'm getting a bit confused reading and re-reading RFC 2518, regarding
locking.
I understand that when a client creates a new lock via a LOCK request,
the server's 200 response includes a body which has a DAV:lockdiscovery
property in it (describing the fields of the new lock).
But what I can't determine.... is 'DAV:lockdiscovery' now a real
property? Meaning, if a PROPFIND to fetch <allprops> of the resource
comes in, does this property now show up in the list?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: dav locking/property question
Posted by Ben Collins-Sussman <su...@collab.net>.
On Dec 13, 2004, at 10:16 AM, Julian Reschke wrote:
>
> Yes, it does. In fact, it should show up always (but be empty when
> there is no lock on the resource).
>
Well hey ho, lookie there! Somehow mod_dav is doing the right thing --
it must be magically generating this liveprop for me. Because
mod_dav_svn sure hasn't been taught about generating the
DAV:lockdiscovery!
Notice that DAV:lockdiscovery seems to be always present, lock or not.
This is a cadaver session against my svn repository:
dav:/svn/testrepos/> lock BLOO
Locking `BLOO': succeeded.
dav:/svn/testrepos/> propget BLOO
Fetching properties for `BLOO':
resourcetype =
getcontentlength = 1294
getcontenttype = text/plain
getetag = "9//BLOO"
creationdate = 2004-12-10T22:59:41.903701Z
getlastmodified = Fri, 10 Dec 2004 22:59:41 GMT
checked-in = <href>/svn/testrepos/!svn/ver/9/BLOO</href>
version-controlled-configuration =
<href>/svn/testrepos/!svn/vcc/default</href>
version-name = 9
creator-displayname = sussman
auto-version = DAV:checkout-checkin
baseline-relative-path = BLOO
md5-checksum = 48e8774205932008d8db5f6ea02e256a
repository-uuid = 1f43ae66-eaea-0310-a737-dfb60bd9b335
supportedlock =
<lockentry>
<lockscope><exclusive></exclusive></lockscope>
<locktype><write></write></locktype>
</lockentry>
lockdiscovery = <activelock>
<locktype><write></write></locktype>
<lockscope><exclusive></exclusive></lockscope>
<depth>0</depth>
<timeout>Infinite</timeout>
<locktoken>
<href>opaquelocktoken:52ecf9be-21eb-0310-a188-c53becac88c3</href>
</locktoken>
</activelock>
dav:/svn/testrepos/> unlock BLOO
Unlocking `BLOO': succeeded.
dav:/svn/testrepos/> propget BLOO
Fetching properties for `BLOO':
resourcetype =
getcontentlength = 1294
getcontenttype = text/plain
getetag = "9//BLOO"
creationdate = 2004-12-10T22:59:41.903701Z
getlastmodified = Fri, 10 Dec 2004 22:59:41 GMT
checked-in = <href>/svn/testrepos/!svn/ver/9/BLOO</href>
version-controlled-configuration =
<href>/svn/testrepos/!svn/vcc/default</href>
version-name = 9
creator-displayname = sussman
auto-version = DAV:checkout-checkin
baseline-relative-path = BLOO
md5-checksum = 48e8774205932008d8db5f6ea02e256a
repository-uuid = 1f43ae66-eaea-0310-a737-dfb60bd9b335
supportedlock =
<lockentry>
<lockscope><exclusive></exclusive></lockscope>
<locktype><write></write></locktype>
</lockentry>
lockdiscovery =
dav:/svn/testrepos/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: dav locking/property question
Posted by Julian Reschke <ju...@gmx.de>.
Ben Collins-Sussman wrote:
> Hey Julian (and others):
>
> I'm getting a bit confused reading and re-reading RFC 2518, regarding
> locking.
For a change, you may want to check whether
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-latest.html>
makes things clearer (feedback appreciated...).
> I understand that when a client creates a new lock via a LOCK request,
> the server's 200 response includes a body which has a DAV:lockdiscovery
> property in it (describing the fields of the new lock).
Yes.
> But what I can't determine.... is 'DAV:lockdiscovery' now a real
> property? Meaning, if a PROPFIND to fetch <allprops> of the resource
> comes in, does this property now show up in the list?
Yes, it does. In fact, it should show up always (but be empty when there
is no lock on the resource).
Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org