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

Re: [whatwg] Fetch Objects and scripts/stylesheets

From: Ben Maurer <ben.maurer@gmail.com>
Date: Mon, 28 Jul 2014 12:12:42 -0700
Message-ID: <CABgOVaKTSaHOuLMEAW_9QX7ZbmQV9AGoHMjzLNiV_2UMZONNSg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Boris Zbarsky <bzbarsky@mit.edu>, William Chan (ι™ˆζ™Ίζ˜Œ) <willchan@chromium.org>
The idea is you could specify any parameter to fetch. For example, if fetch
allowed you to specify an HTTP/2 priority, you could specify that.

As a concrete example of why passing a header might be useful, Facebook
uses an automated pipeline to decide what CSS/JS files to package together.
If we could pass a custom header in the request for a CSS file (for
example: what part of the page caused that file to be loaded) we could use
this information in our packaging system to make smarter decisions. While
we do have the referrer header, a piece of interactive javascript on a page
might be the cause of the CSS file being required. A custom header would
allow logging this.




On Mon, Jul 28, 2014 at 11:34 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Mon, 28 Jul 2014, Ben Maurer wrote:
> >
> > What about initial parameters to fetch (vs modifications you could make
> > in flight via the myfetch object). Would there be an attribute of <link>
> > that you could use to pass parameters to fetch (eg a custom header)?
>
> What's the use case here? Why are we trying to send custom headers on a
> <link>?
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
Received on Monday, 28 July 2014 19:13:07 UTC

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