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

RE: Operations not Atomic (was: bind draft issues)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 3 Mar 2003 23:09:08 +0100
To: "Brian Korver" <briank@xythos.com>, "WebDAV" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCGEDJGKAA.julian.reschke@gmx.de>

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Brian Korver
> Sent: Monday, March 03, 2003 8:36 PM
> To: WebDAV
> Subject: Re: Operations not Atomic (was: bind draft issues)
>
>
>
> On Saturday, March 1, 2003, at 06:27  AM, Clemm, Geoff wrote:
> >
> >    From: Brian Korver [mailto:briank@xythos.com]
> >
> >    Operations not Atomic
> >
> >    None of the operations specified should be required
> >    to be atomic.  I'd prefer SHOULD NOT myself.  This is
> >    especially true for any operation that involves deleting
> >    collections.
> >
> > Atomic operations are one of the primary purposes of the
> > binding protocol.  A server that cannot maintain atomic
> > MOVE/DELETE/BIND operations is not capable of supporting
> > the bind protocol.
>
> Geoff,
>
> I disagree strongly.  Nothing should be stated to prohibit
> atomic operations, but the spec should leave this decision
> up to implementors.  There can be perfectly valid reasons
> why a server vendor might want to provide normal filesystem
> semantics to users.

Brian,

I can follow for DELETE (see separate mail), but I'm at a loss about how
MOVE and BIND can be non-atomic. Could you please explain?

Julian


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

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