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

Re: [whatwg] Fetch API Polyfill

From: David Graham <david.malcom.graham@gmail.com>
Date: Tue, 14 Oct 2014 10:08:04 -0600
Message-ID: <CAK=8WGYN3sCxCXBFhP6uM94E9hL0p_e9ZKR4PDzDz-_5eT3EQw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>
Interesting—thanks for the clarification. I've updated the example from this

    fetch('/users.html').then(function(response) {
      document.body.innerHTML = response.body
    })

to this

    fetch('/users.html')
      .then(function(response) {
        return response.text()
      }).then(function(body) {
        document.body.innerHTML = body
      })

Should `response.body` ever be used directly or only accessed through
one of the response body promises (json, text, blob, arrayBuffer,
formData)?

On Tue, Oct 14, 2014 at 4:03 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Tue, Oct 14, 2014 at 1:15 AM, David Graham
> <david.malcom.graham@gmail.com> wrote:
>> We’re developing a polyfill for the new Fetch API at GitHub:
>>
>>    https://github.com/github/fetch
>>
>> The spec was fairly easy to follow, but I’d love any feedback on places the implementation could be improved. Fetch is probably the most exciting new browser API since querySelectorAll.
>
> The example in README.md suggests your promise resolves too late. It
> needs to resolve when all the HTTP headers are in. The body can then
> be accessed through a series of promise methods. (And in the future
> you can have access to a stream at that point as well.)
>
>
> --
> https://annevankesteren.nl/
Received on Tuesday, 14 October 2014 16:08:30 UTC

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