W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Streams and Blobs

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 15 Mar 2013 17:23:21 -0700
Message-ID: <CA+c2ei83Bi3yQYJMZ3MWsb5Os9m2_tAD+G+muq48fBjphtNTLg@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Anne van Kesteren <annevk@annevk.nl>, WebApps WG <public-webapps@w3.org>
On Fri, Mar 15, 2013 at 2:36 PM, Glenn Maynard <glenn@zewt.org> wrote:
>> I guess we could always make the Stream object immediately produce an
>> error if .responseType is changed to something other than "stream".
>
> Specifically, I'd recommend that when readyState isn't UNSENT, setting
> responseType to "stream" should fail, and if readyState is set to "stream"
> then setting it to something else should fail.  That is, once the request is
> started it's too late to change into or out of stream mode.

That would mean not supporting the ability to choose to handle a
response as a Stream based on metadata in the response. That was the
reason we decided to support setting .responseType in the
HEADERS_RECEIVED state to other values. I don't see why the same
reasons doesn't apply here.

/ Jonas
Received on Saturday, 16 March 2013 00:24:19 GMT

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