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

Re: WebDAV sync last call

From: Andrew McMillan <andrew@morphoss.com>
Date: Wed, 14 Dec 2011 22:29:42 +1300
Message-ID: <1323854982.6059.52.camel@dave.home.mcmillan.net.nz>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Cyrus Daboo <cyrus@daboo.name>, w3c-dist-auth@w3.org
On Wed, 2011-12-14 at 09:54 +0100, Julian Reschke wrote:
> 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).

Yes, those are good points.


andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
           This fortune is inoperative.  Please try another.

Received on Wednesday, 14 December 2011 09:30:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 14 December 2011 09:30:21 GMT