Cyrus Daboo wrote:
I am not convinced the use of Depth in sync report is violating the
definition in 3253. In some ways it is a matter of how you look at the
sync. Your viewpoint is that the report asks the collection for its
changes - in that case, yes, Depth:0 would apply. The other view is
Julian Reschke wrote:
On 2011-12-14 18:01, Ken Murchison wrote:
Cyrus Daboo wrote:
I am not convinced the use of Depth in sync report is violating the
definition in 3253. In some ways it is a matter of how you look at the
sync. Your viewpoint is that the report asks the collection for its
On 14/12/2011 18:27, Cyrus Daboo wrote:
A member URI MUST be reported as changed if its mapped resource's
entity tag value (defined in Section 3.11 of [RFC2616]) has changed
since the request sync-token was generated.
It should be mentioned that this only works well with resources
that are
Hi Julian,
--On December 14, 2011 12:10:27 AM +0100 Julian Reschke
julian.resc...@gmx.de wrote:
On 2011-12-02 00:41, The IESG wrote:
...
Abstract
This specification defines an extension to WebDAV that allows
efficient synchronization of the contents of a WebDAV collection.
-
On 2011-12-14 17:06, Cyrus Daboo wrote:
Hi Julian,
--On December 14, 2011 12:10:27 AM +0100 Julian Reschke
julian.resc...@gmx.de wrote:
On 2011-12-02 00:41, The IESG wrote:
...
Abstract
This specification defines an extension to WebDAV that allows
efficient synchronization of the contents
On 2011-12-14 18:01, Ken Murchison wrote:
Cyrus Daboo wrote:
I am not convinced the use of Depth in sync report is violating the
definition in 3253. In some ways it is a matter of how you look at the
sync. Your viewpoint is that the report asks the collection for its
changes - in that case,
Hi Julian,
--On December 14, 2011 5:29:16 PM +0100 Julian Reschke
julian.resc...@gmx.de wrote:
I am not convinced the use of Depth in sync report is violating the
definition in 3253. In some ways it is a matter of how you look at the
It does.
RFC 3253 defines the response format for Depth
Hi Ken,
--On December 14, 2011 12:29:18 PM -0500 Ken Murchison
mu...@andrew.cmu.edu wrote:
D:sync-result
... other collection props the report asked for ...
D:sync-tokenhttp://example.com/ns/sync/1234/D:sync-token
/D:sync-result
I don't necessarily see a problem with sync report using
On 2011-12-14 18:27, Cyrus Daboo wrote:
Hi Julian,
--On December 14, 2011 5:29:16 PM +0100 Julian Reschke
julian.resc...@gmx.de wrote:
I am not convinced the use of Depth in sync report is violating the
definition in 3253. In some ways it is a matter of how you look at the
It does.
RFC
On 2011-12-14 18:34, Cyrus Daboo wrote:
Hi Ken,
--On December 14, 2011 12:29:18 PM -0500 Ken Murchison
mu...@andrew.cmu.edu wrote:
D:sync-result
... other collection props the report asked for ...
D:sync-tokenhttp://example.com/ns/sync/1234/D:sync-token
/D:sync-result
I don't necessarily
On 2010-06-08 09:14, Julian Reschke wrote:
On 07.06.2010 17:11, Werner Donné wrote:
Hi,
I don't see why Depth:infinity should be ruled out from the start. You
can let the server decide if the performance penalty is too high or
not. A server with a relational system underneath it, for example,
On 2011-12-02 00:41, The IESG wrote:
...
Abstract
This specification defines an extension to WebDAV that allows
efficient synchronization of the contents of a WebDAV collection.
- Expand acronyms on first use.
Typically, the first time a client connects to the server it will
The IESG has received a request from an individual submitter to consider
the following document:
- 'Collection Synchronization for WebDAV'
draft-daboo-webdav-sync-06.txt as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.
13 matches
Mail list logo
