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

I think the main problem with your sketch is that it's not opt-in and uses confusing terminology. I think by default a service worker should remain in control of all networking activity. It can relinquish some of that control back to the browser, but that should be opt-in. The terminology should make it clearer that this affects navigation only (only top-level presumably?).

Even then, I'd still like to hear from Apple, Microsoft, and Mozilla's e10s team what their thoughts are on this (and also Servo). Would love to have some insight as to how much this relates to Chrome architecture decisions vs overall browser architecture.

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