W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2003

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 3 Mar 2003 23:08:02 +0100
To: "Clemm, Geoff" <gclemm@rational.com>, "WebDAV" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCCEDJGKAA.julian.reschke@gmx.de>

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Clemm, Geoff
> Sent: Monday, March 03, 2003 10:44 PM
> To: WebDAV
> Subject: RE: Move and Delete (was: bind draft issues)
>
>
>
> To emphasize an earlier comment, it is true that the bind protocol
> places constraints on how a server is allowed to implement the DELETE
> and MOVE methods.  In particular, a server that supports the bind
> protocol is not allowed to do a partial MOVE or a partial DELETE (even
> though 2518 allows it).
> ...

Good catch. I remember that we discussed that at some point of time, but it
seems it was never added to the issues list.

Our server indeed is able to support the BIND method and live properties
with all their semantics, yet won't do an atomic DELETE on collections. I
agree that *technically* a server that properly handles bindings *could* do
atomic deletes, but in reality, there may be reasons why you don't *want*
to.

Therefore, I'd like the spec not to require a specific behaviou, or, as a
minimum, change the MUST to a SHOULD.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Monday, 3 March 2003 17:08:14 GMT

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