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

Re: Fetch API

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 3 Jun 2014 17:50:06 +0200
Message-ID: <CADnb78jDLof7FWYPqNfYW9MAWWa5ATiAFne7=+aiH-uuX=HkAQ@mail.gmail.com>
To: Domenic Denicola <domenic@domenicdenicola.com>
Cc: public-script-coord <public-script-coord@w3.org>, Joshua Bell <jsbell@chromium.org>, Jungkee Song <jungkee.song@samsung.com>, Yehuda Katz <wycats@gmail.com>, Alex Russell <slightlyoff@google.com>, Jonas Sicking <jonas@sicking.cc>, Jake Archibald <jaffathecake@gmail.com>, Tobie Langel <tobie.langel@gmail.com>, WebApps WG <public-webapps@w3.org>
On Sun, Jun 1, 2014 at 8:06 AM, Domenic Denicola
<domenic@domenicdenicola.com> wrote:
> - HeaderMap should have a constructor that takes an iterable of [key, value] pairs, in the same way Map does.

Yeah, waiting for IDL hooks that would work here ;-)

> - I like HeaderMap a lot, but for construction purposes, I wonder if a shorthand for the usual case could be provided. E.g. it would be nice to be able to do
> fetch("http://example.com", {
>   headers: {
>     "X-Foo": "Bar"
>   }
> });
> instead of, assuming a constructor is added,
> fetch("http://example.com", {
>   headers: new HeaderMap([
>     ["X-Foo", "Bar"]
>   ])
> });

Yeah, it's not clear to me what is best here. An object whose keys are
ByteString and values are either ByteString or a sequence of
ByteString? I agree that we want this. Part of the problem here is how
to best represent HTTP headers. See
https://github.com/slightlyoff/ServiceWorker/issues/300 for more

Received on Tuesday, 3 June 2014 15:50:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC