W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1999

Re: DELETE Semantics

From: <jamsden@us.ibm.com>
Date: Fri, 24 Sep 1999 16:05:53 -0400
To: w3c-dist-auth@w3.org
Message-ID: <852567F6.006EBB34.00@d54mta03.raleigh.ibm.com>






From: Jason Crawford on 09/24/99 03:56 PM

To:   jamsden@us.ibm.com
cc:   w3c-dist-auth@w3.org

Subject:  Re: DELETE Semantics  (Document link: Jim Amsden)


<ja>
1. all URL references to a resource are bindings, including the PUT or MKCOL
used to create the resource in the first place.
</ja>

Just to clarify.  I think you're suggesting that PUT and MKCOL are
operations on bindings.  I agree... they create new bindings, if
there isn't a resource there
already.  But in the case of PUT, if there's a (non-collection) resource
already there, then it's an action on the resource... not the binding.

<jra>
Yes
</jra>

<ja>
4. LOCK locks the resource, not the bindings. If the namespace needs to be
controlled, then the user should lock the applicable parent collections.
</ja>

<jlc>
I agree that that's what seems to be suggested.  I just want to add, "ouch!
That's a painful way to protect a URI.".
</jlc>

<jra>
Then what are collections for if not to manage and control the namespace? What
else could locking a collection mean? Note that it does not have to be a deep
lock.
</jra>
Received on Friday, 24 September 1999 16:11:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:51 GMT