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

@delapuente, at the last f2f I think we decided that preflight was pretty tangential to routing. In this case we aren't trying to define behaviors to bypass the service worker or to race the network and cache. We simply want the request to be sent out without incurring the full service worker startup cost. Then once the service worker has started it can get the request and presumably use the resulting stream and maybe mix stuff from that stream and cache. But it's still totally up to the service worker.

The preflight api as talked about at the f2f is the simplest, most performant and broadest solution that we could come up with for this. Routing is another beast altogether.

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