Re: [whatwg/fetch] Define the "Preload Cache" (#590)

One thing that might make sense here is to make use of `cache-control: immutable` (already shipped in Safari/Firefox, [bug open](https://bugs.chromium.org/p/chromium/issues/detail?id=611416) in Chrome).

Something like:
- Preloaded responses without `immutable` go to the regular cache, equivalent to `<script>fetch(link.href)</script>`
- Preloaded responses with `immutable` are kept in memory throughout the lifetime of their `link` element and served from there for eligible clients.

This allows fine-grained control over the cache both from the server and from the client.




-- 
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/590#issuecomment-927328127