W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2014

Re: [whatwg] [Fetch] ambiguity problem?

From: Brian Kardell <bkardell@gmail.com>
Date: Tue, 12 Aug 2014 10:40:39 -0400
Message-ID: <CADC=+jfZbw1-exc8CR+xtQNKneZCQTocU3Ah_1xxPq1Nk_b61g@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>
On Aug 12, 2014 9:13 AM, "Anne van Kesteren" <annevk@annevk.nl> wrote:
>
> On Tue, Aug 12, 2014 at 3:07 PM, Brian Kardell <bkardell@gmail.com> wrote:
> > Not wanting to start a giant bikeshed here but if you have a look at
Jake's
> > Service Worker Examples as an early use of fetch and streams, it seems
> > clear that many developers would be surprised by behavior of not being
> > about to refer back to the response body.
>
> Why? XMLHttpRequest does the same thing.
>
>
> --
> http://annevankesteren.nl/

In what way? . response is a completely read DOMString or Object or
whatever, not a Stream?
Received on Tuesday, 12 August 2014 14:41:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:22 UTC