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

RE: v6 comments - multistatus responses

From: Yaron Goland <yarong@microsoft.com>
Date: Wed, 4 Feb 1998 00:21:40 -0800
Message-ID: <3FF8121C9B6DD111812100805F31FC0D0113C800@red-msg-59.dns.microsoft.com>
To: "'Dylan Barrell'" <dbarrell@opentext.ch>, "'WebDAV'" <w3c-dist-auth@w3.org>
Ahhh.. now I understand. Yes my dear Dylan, you are missing something by
reading the paragraph out of context. The sentence is included in a
paragraph explaining the format of a 207 Multi-Status response. Thus the
client HAS received a response, it may not contain any PROP elements, but it
is a full, properly formatted response. Note, btw, that if everything works
just perfectly the server should send a 200 Success and call it a day.
Either way the client does get a response. If the client gets no response
then it can assume nothing.

		Yaron

> -----Original Message-----
> From:	Dylan Barrell [SMTP:dbarrell@opentext.ch]
> Sent:	Tuesday, February 03, 1998 4:52 PM
> To:	Yaron Goland; 'WebDAV'
> Subject:	RE: v6 comments - multistatus responses
> 
> You can say what you want I still don't like the fact that the paragraph
> ends with the sentence ".....As such the client may safely assume that a
> resource was deleted successfully if no response is returned.". This
> implies that a client could send a delete request, the server cuts the
> connection and the client has to assume that the delete request was
> successful (or am I missing something reading this paragraph out of
> context).
> 
> Cheers
> Dylan
> 
> -----Original Message-----
> From:	Yaron Goland [SMTP:yarong@microsoft.com]
> Sent:	Tuesday, February 03, 1998 8:35 PM
> To:	'Dylan Barrell'; 'WebDAV'
> Subject:	RE: v6 comments - multistatus responses
> 
> BTW, I actually changed the "MUST"s to "SHOULD"s. Thus a server has the
> right to return 424 and 204 but shouldn't unless they have a damn good
> reason.
> 
> As for requiring confirmation of success, that would be unreasonably
> verbose. If you copy 10,000 files you will end up with 10,000 success
> statements. Given that we have defined, in an absolutely deterministic
> way,
> the result without requiring extra bytes on the wire, I think we have done
> the whole world a favor.
> 
> 		Yaron
> 
> > -----Original Message-----
> > From:	Dylan Barrell [SMTP:dbarrell@opentext.ch]
> > Sent:	Tuesday, February 03, 1998 2:02 AM
> > To:	Yaron Goland; 'WebDAV'
> > Subject:	RE: v6 comments - multistatus responses
> > 
> > I would prefer to require that a server MUST return a confirmation of
> the
> > success of the operation rather than the client simply assuming that the
> > operation succeeded if absolutely no response is received.
> > 
> > Cheers
> > Dylan
> > 
> > -----Original Message-----
> > From:	Yaron Goland [SMTP:yarong@microsoft.com]
> > Sent:	Friday, January 30, 1998 9:17 AM
> > To:	'Dylan Barrell'; 'WebDAV'
> > Subject:	RE: v6 comments - multistatus responses
> > 
> > ..... 
> > If an error occurs with a resource other than the resource identified in
> > the
> > request URI then the response MUST be a 207 Multi-Status.  424 Method
> > Failure errors MUST NOT be in the 207 Multi-Status.  They can be safely
> > left
> > out because the client will automatically know that the ancestors of a
> > resource could not be deleted when the client receives an error for the
> > ancestor's progeny.  Additionally 204 No Content errors MUST NOT be
> > returned
> > in the 207 Multi-Status.  The reason for this prohibition is that 204 No
> > Content is the default success code.  As such the client may safely
> assume
> > that a resource was deleted successfully if no response is returned.
> > ....... 
> 
Received on Wednesday, 4 February 1998 03:22:01 GMT

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