Justin Erenkrantz wrote:
> ...
> Take a look at RFC 2518 Section 13.8 for what I mean. WebDAV reports
> the presence of a lock by responding to a lockdiscovery PROPFIND
> request. This is how 'svn info' for a lock would likely be implemented
> over WebDAV.
>
> So, back to my question: does the fact that the property of a resource
> implicitly changes because a lock has been acquired or released also
> mean that the global rev number also changes? By and large, our
> response has been that if any property changes, so should the repository
> revision. Although I feel that might not be appropriate here. I've
> found the WebDAV and DeltaV specs to be completely unhelpful here. My
> hunch is that they shouldn't (and is permitted by DeltaV), but I'm not
> 100% sure. I'm going to ask some of the WebDAV folks around the office
> though... -- justin
The main question here is whether locks contribute to the
version-controlled state of a resource. If it did, some of the
autolocking behaviours allowed by RFC3253 (because they rely on the
ability to lock a resource that is not checked-out) wouldn't work.
Best regards, 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
Received on Thu Oct 14 09:37:36 2004