Re: [whatwg/fetch] Allow service-workers mode to be set in fetch options (#492)

@mattto, there's always the possibility of having to wait for the service worker event loop and starting and doing IPC's to talk to a service worker will never be free. Like I said in the issue linked to above "If we send 40 or so requests from the window at once, while the first few may be quick, the other events get tacked onto the end of the Service Worker event loop and end up getting delayed quite a bit before they can hit the network". There are many cases when the developer knows that something won't be available from within the service worker and in those cases it's silly to hurt performance by going through the sw when the developer already knows that it's a waste.

In terms of how this relates to static routing, this is orthogonal. Static routing is declarative and is not flexible to cases when we know that we have a new url that the service worker has no clue about.

-- 
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/492#issuecomment-283990541