Re: [w3c/ServiceWorker] Eliminating SW startup latency for common case (#920)

Aside, @NekR I don't get why we need the `RequestStorage`, could you clarify, please?

And, for clarification: suppose a _preflight_ request is so fast that it answers completely before waking the service worker up? What happen then? Is that response used ignoring to trigger `fetch` to the sw? Or are we always waiting for the sw anyway? If the latter is the case, perhaps rather than _preload_ or _preflight_, what we want is something like _ping_:

```js
navigator.serviceWorker.register('sw.js', {
  routes: {
    'some/route': new PingNetwork(),
    'some/other/route': new PingNetwork({ headers: ..., tttl: ... })
  }
});
```


-- 
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-241861365