[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-19 10:26:36 CET

Julian Reschke <julian.reschke@gmx.de> writes:

> Ben Collins-Sussman wrote:
> > 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.
> But *that's* a feature that RFC2518bis aware clients *can* expect to work.

Say what?! Julian, will you please explain what is and isn't needed
support-wise across the following four areas of LOCKNULL support:

   - LOCK on a NULL resource
   - UNLOCK on a NULL resource
   - PROPFIND on a LOCKNULL resource
   - Revelation of immediate LOCKNULL children of normal collections

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 19 10:31:10 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.