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

Here's a little shopping list of features. To those building sites, which is the minimum that solves the problems you have? Which features are more than you'll ever need?

1. When the user navigates to my site I want to ping a URL with some sort of credential. I'm happy for the actual navigation request to go through the service worker and therefore be delayed by it starting up, but the ping should be sent before SW startup.
  1. I don't care about the response of the ping
  1. I want to handle the response of the ping, but I don't intend to use it in response to a fetch event within the next few seconds
  1. I want to handle the response of the ping, and I'm likely to use it in response to a fetch event in the next few seconds
1. When the user navigates to my site, I want a network request for the navigation to race SW startup & response. If the SW manages to win, at least the network request served as a ping.
1. When the user navigates to my site I want to perform a series of network preloads while the SW is starting up
  1. I want those preloads to bypass the service worker completely
  1. I want the request to bypass the SW, but I want the SW to process the response
  1. I want one of the above depending on the URL
1. I want to declare the behaviour (serve from cache, serve from network) for particular requests (depending on URL, type, & headers) up front so the browser can respond without starting the SW

+@bmaurer @n8schloss

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/920#issuecomment-233913390