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

Re: Collection Synchronization for WebDAV

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 31 Jul 2007 17:57:46 +0200
Message-ID: <46AF5BFA.2040102@gmx.de>
To: Arnaud Quillaud <arnaud.quillaud@sun.com>
CC: w3c-dist-auth@w3.org

Julian Reschke wrote:
> 
> Arnaud Quillaud wrote:
>> Some comments:
>>
>> 1) It is specified that "The "Depth" header MUST be ignored by the server
>> and SHOULD NOT be sent by the client". But, unless I missed it, there 
>> is no
>> mention of the actual depth of the report. I'm assuming it is 1 but maybe
>> that is not what you had in mind. It would be worth making it clear.
>> ...
> 
> Agreed. Please stay compatible with the REPORT framework. That is,
> ...

Speaking of which, please make sure to stay compatible with RFC3253, 3.6 
(<http://greenbytes.de/tech/webdav/rfc3253.html#rfc.section.3.6>):

"If a Depth request header is included, the response MUST be a 207 
Multi-Status. The request MUST be applied separately to the collection 
itself and to all members of the collection that satisfy the Depth 
value. The DAV:prop element of a DAV:response for a given resource MUST 
contain the requested report for that resource."

That essentially means that if the response format for Depth:0 is a 
DAV:multistatus, the result for Depth:1 will be many multistatus bodies 
embedded into a multistatus container element.

I guess it's really time to extract the definition of the REPORT method 
from RFC3253, and move it it a separate doc with lots of examples... 
(will start on it soon).

Best regards, Julian
Received on Tuesday, 31 July 2007 15:57:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 20:02:55 UTC