W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2011

Re: WebDAV sync last call

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 14 Dec 2011 09:54:47 +0100
Message-ID: <4EE86457.8060100@gmx.de>
To: andrew@morphoss.com
CC: Cyrus Daboo <cyrus@daboo.name>, w3c-dist-auth@w3.org
On 2011-12-14 08:29, Andrew McMillan wrote:
> ...
> (2) long polling
> When I make a sync request I would sometimes like to be able to indicate
> to the server that it is acceptable for it to treat my request as a
> "long poll", so that the server would hold my connection open until a
> change occurred within the hierarchy of the request.
> For a server to do this, I think that it would be advantageous for the
> old sync token to be provided within the request headers, rather than
> within the XML payload of the request.  I believe that doing this would
> make server processing easier, since all necessary data for deciding
> whether changes have occurred (URL, Depth, Token) would be in the
> headers.
> ...

How does this help? The request body fur the REPORT is sufficiently 
small to be inspected right away, no?

The important part for the ability to stream the change events is that 
the new sync token is last in the response body, and the sync spec got 
that right...

(Mentioning this because I'm using Atom for a similar use case in JCR, 
and that suffers from the ETag having to be sent out first, with 
libraries and server frameworks having no support for trailers).

Best regards, Julian
Received on Wednesday, 14 December 2011 08:55:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:39 UTC