RE: Move and Delete (was: bind draft issues)

> > 2518 correctly states that MOVE (and COPY) also may involve
> > a DELETE with "Depth: infinity" operation in the case of
> > overwrite.
> It supports that.  What you're possibly refering to is the fact that
> 2518 let's the DELETE on a collection to delete some of the
> children and abort before removing the colection itself and without
> backing out what it did.   In the Bind Spec, there is no requirement
> to unbind those child resources and in many cases you definitely
> don't want to do that.   You only have to unbind the collection.
> There is no partial DELETE.  You just have to unmap that collection.
> Whether that reclaims resources is a different matter.

Would you be able to do that -- unmap a collection -- even if one of its
children were locked? The person with the lock would then lose it and
their resource, right?

If on the other hand, you can't unmap a collection until all its
children are unlocked, then you have a serious problem supporting that
atomically on a filesystem. For example, by the time IIS 5.0 checks all
the children of a collection to see if they're locked, one of them might
have just gotten a new lock.  

Lisa

Received on Monday, 3 March 2003 22:53:12 UTC