Re: [whatwg/fetch] preload, destinations, and module scripts (#486)

> Compared to HTTP/2, the benefits are tiny, whereas if we can create something module-specific that takes care of all the module-related pieces for us and avoids loading the bytes into two separate caches, we're in much better shape.

The cancellation time of HTTP/2 PUSH is a huge problem for avoiding cache redundancy. The best shape for the web is one where a module graph doesn't even have to make a request to the network - which is the goal I'm after here.

We don't need network-based preload for this - we need a flat hinting scheme which preload can offer us.

I don't actually care about the rel to be perfectly honest - the above is all I'm interested in. But please think ahead to the new parsing formats of the web if designing a new rel - that's the combinatorial explosion to worry about.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/486#issuecomment-324744654