W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [XHR] chunked

From: Wenbo Zhu <wenboz@google.com>
Date: Thu, 7 Jun 2012 02:30:34 -0700
Message-ID: <CAD3-0rMy6c7-mHkaYt_yaazbQrt5z0PnPDzAXckCkbf8pEM2-g@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: public-webapps WG <public-webapps@w3.org>
On Thu, Jun 7, 2012 at 2:14 AM, Henri Sivonen <hsivonen@iki.fi> wrote:

> On Thu, May 24, 2012 at 8:59 AM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> > On Thu, May 24, 2012 at 2:54 AM, Jonas Sicking <jonas@sicking.cc> wrote:
> >> Is there a reason not to add "chunked-text" and "chunked-arraybuffer"
> >> to the spec right now?
> >
> > 1. Why not just have
> > http://html5labs.interoperabilitybridges.com/streamsapi/ to address
> > this case?
>
> It appears that Microsoft's proposal involves potentially buffering
> the XHR response body until the Web author-supplied script chooses to
> initiate I read from the stream object. Or am I missing something?
>
> The "chunked-text" and the "chunked-arraybuffer" response types are
> both simpler than the stream proposal and have the advantage that they
> don't involve the browser engine buffering the XHR response body: if
> the Web author-provided script fails to handle the chunks as they
> arrive, the data is gone and doesn't fill up buffer space.
>
Yes, this will be the desired behavior.

>
> (Some of my remarks on IRC were confused, because I mistook the
> Worker-specific API for the API proposed for the main thread.)
>
> --
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
>
>
Received on Thursday, 7 June 2012 09:31:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT