[w3c/ServiceWorker] Priority of requests (feature request) (#1137)

Hello everyone

The goal is to speculatively load all static resources as soon as possible and store them permanently (and manage them on-demand) without blocking page that is being viewed.

I am looking for a solution to create efficient **persistent** prefetch of selected (static) resources that could be stored for later use with **parallel** download, but without **blocking** other on-demand requests.

As for the googled solution to the problem:
1, Issue with <link rel="prefetch"> or <link rel="preload"> is, that it is stored in HTTP cache - which will get flushed without me having anything to say into it. I also have no means of knowing when did the resources get preloaded (to store them in cache api) for precache or how to continue downloading resources during navigation (preload).
2, Inside service worker I haven't found any means of how to set low priority to request (HTTP/2) as not to block other on-demand requests. Workaround for this is fetching one resource at a time - which is not as efficient or monitor all the traffic (should be impossible from userspace if I am correct).


Did I maybe miss something what could be done?
Sorry if this is not a correct place to write such suggestion. Maybe you could direct me for the future.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1137