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

RE: Issues PUT_AND_INTERMEDIATE_COLLECTIONS and INTEROP_DELETE_AND_MULTISTATUS

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 24 Jan 2003 23:13:25 +0100
To: <w3c-dist-auth@w3c.org>
Message-ID: <JIEGINCHMLABHJBIGKBCMEPBGEAA.julian.reschke@gmx.de>

OK,

here's my proposal then:


1) define:

425 Incomplete Operation
The 425 (Incomplete Operation) status code means that the method could not
be performed completely because it wasn't executed atomically and the
request could not be applied to all affected child resources.

2) deprecate marshalling of multistatus with 207 on failures or incomplete
operations

3) allow multistatus response body for 424 (failed dependancy) and 425.

Note that 424 could be used when the whole operations was rejected because
of an error on a child resource (such as deep locks that are in conflict
with child lock -- another open issue for error marshalling), while 425
would be returned when the method "partly" succeeded (like a DELETE that
couldn't remove one specifc child, but many others).

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Friday, January 24, 2003 10:49 PM
> To: 'Julian Reschke'; 'John DeSoi'; w3c-dist-auth@w3c.org
> Subject: RE: Issues PUT_AND_INTERMEDIATE_COLLECTIONS and
> INTEROP_DELETE_AND_MULTISTATUS
>
>
>
>
> > That being said, from a consistency p.o.v. I agree. I'll
> > assume for a moment
> > that few WebDAV clients indeed *do* evaluate a 207 on DELETE
> > (and other
> > candidates such as LOCK/COPY...), and those probably would be easy to
> > upgrade. If this is true, all we'd need to do is
> >
> > - deprecate status of 207 for failures
> > - introduce a new 4xx code such as INCOMPLETE OPERATION which
> > would carry
> > the same multistatus body
> >
> It doesn't seem nearly that big a change is necessary. The biggest
> change I'd consider given what I currently know, is that the spec would
> require that HTTP 1.1 method requests to non-collections should not
> result in 207. This would only affect the definition for DELETE, since
> that's the only HTTP 1.1 method that is defined defined as returning
> 207. DELETE could still return 207 in response to a Depth: infinity
> request to a collection.
>
> My reasoning is that HTTP clients address individual pages with DELETE
> requests, not collections.
>
> lisa
>
>
Received on Friday, 24 January 2003 17:14:01 GMT

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