- From: Ben Maurer <ben.maurer@gmail.com>
- Date: Fri, 15 Aug 2014 08:38:48 -0700
- To: Ilya Grigorik <igrigorik@gmail.com>
- Cc: WHATWG <whatwg@whatwg.org>
Hey, Thanks for writing this up! So to the extent we are simply exposing http/2 semantics, this spec seems pretty clear. Two questions that I have that aren't answered by the http/2 spec: - What do we expect the browser to do with priorities set cross domain. Eg, if I express that a.com/foo.js depends on b.com/bar.js, does the browser do anything about this. What if b.com/bar.js depends on a.com/blah.js. Would we tell a.com that foo.js depends on blah.js? - Developers might have something they would want to speculatively fetch only if http/2 is being used (and therefore they know the resource won't compete for bandwidth with other resources). Maybe this could be solved by simply allowing the user to tell if the browser supports http/2. A more advanced solution could be to allow the user to say "don't send this fetch request unless it's over http/2". One other thing I didn't see any mention of in the write up -- it could be useful to change priority while the request is in flight. http/2 supports this, so it'd be great if this spec could expose it. On Thu, Aug 14, 2014 at 6:16 PM, Ilya Grigorik <igrigorik@gmail.com> wrote: > (followup / continuation of [1]) > > Trying to hash out some ideas for how to connect Fetch and the new > transport capabilities of HTTP/2. Would love to hear everyone's thoughts: > > > https://docs.google.com/document/d/1jSpWc6jkrUoYtGWcxev9Blkkv9RhoO1XtqinBvXqhgY/edit > > ig > > [1] > http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-July/297257.html >
Received on Friday, 15 August 2014 15:39:13 UTC