Re: Locking non-existent paths. Time to discuss.

On Mar 18, 2005, at 3:31 PM, Julian Reschke wrote:
>
> That's correct, it will fail. Back when the WG made the decision to
> deprecate lock-null resources, there was no evidence of clients
> actually relyong on the behaviour (if they did, they wouldn't work
> with IIS, as far as I can remember).
>

Well, we've already got minimal lock-null support working, so it's
probably easier to keep things as they are.

Mike has removed his support for listing lock-null children in
collections, since it's a lot of complexity for a feature that no
current clients use, and no future clients *should* use.

So our plan will be:

  --> Allow generic DAV clients to LOCK/PROPFIND/UNLOCK nonexistent urls.

  --> Don't allow svn clients to 'svn lock' nonexistent urls, nor
      lock schedule-add paths.

  --> Allow 'svn unlock' to remove a lock on a nonexistent url.

The last bit probably isn't necessary, but it already works, and it's a
bit of insurance in case a DAV client crashes after locking a
nonexistent url. In practice, we expect these lock-null objects to
exist only for a fraction of a second, not long enough to interfere
with svn clients.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 18 23:21:17 2005