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
On Fri, Aug 15, 2014 at 8:38 AM, Ben Maurer ben.mau...@gmail.com wrote:
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
On Thu, 14 Aug 2014, Ilya Grigorik wrote:
Trying to hash out some ideas for how to connect Fetch and the new
transport capabilities of HTTP/2.
It would be great to get a set of use cases describing what your proposal
is addressing, since that would more easily let people evaluate whether
Some cases I can think of off the top of my head:
- A website has a page where media is the primary content. It would like to
make sure that media is downloaded before JS (example: you go to
flicker.com/my-image, the browser should probably prioiritize that image
over a pice of javascript that is
(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]
