Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920)

At the risk of sounding very stupid (I do not know inner workings of browser and potentional security problems).

Wouldn't it be simpler to just define a way to unsubscribe some requests from service workers (e.g. what @jakearchibald proposed with .declareRoute and FetchSource) AND creating an API that could manipulate browser HTTP cache (not cache api).
The end result would be that developers would be able to set (from js) aggressive max-age + expires headers (which developers should already know) on critical-path requests (hence not waiting for them even if they are subject to occasional change) without waiting for service worker to startup or waiting for any other API. 
The added benefit would be, that developers would get means to update long-living (static) requests/resources upon webpage facelift/redesign without need to use some kind of hack (?v=X).

-- 
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/920#issuecomment-258832815