Re: REBIND a parent to a child

>
> ---------- Forwarded message ----------
> From: Julian Reschke <julian.reschke@gmx.de>
> Date: Oct 25, 2006 6:08 AM
> Subject: Re: REBIND a parent to a child
> To: Chetan Reddy <chetanreddy@gmail.com >
> Cc: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
>
> Chetan Reddy schrieb:
> > The last three mails have confused me a bit.
> > A request to rebind /a to /a/b:
> > Request-URI    /a (identifies a collection resource R1)
> > segment          b
> > href                 /a
> >
> > case 1: /c is also bound to R1
> > case 2: /a is the only binding to R1
> >
> > I think case 1 should succeed(with /c and /c/b both pointing to R1 and
> > /a not existing anymore) and case 2 should fail.
>
> I would agree that if the request succeeds in case 1, that's what the
> outcome should be.
>
> I'm not sure whether case 2 needs to fail, but that's certainly what I
> would do.
>
> > In general, if the collection identified by the Request-URI is not
> > reachable from root after removing the  old binding(href), the server
> > should fail the request.
> > Is that correct?
>
> I'm not sure it needs to, but it's certainly a plausible approach.
>

If the collection identified by Request-URI is not reachable from root after
the old binding is removed (the old binding MUST be removed for the
DAV:binding-deleted postcondition to hold) then the DAV:new-binding
postcondition will not hold as the new binding will not be reachable from
root. Hence, i think the server MUST fail the request.

Chetan