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

@asutherland it seems to me that all these things (declarative routing or a preflight) would be hung off a service worker rather than the registration. As in if V1 sets these things, but V2 doesn't, they're gone. That's closest to how the fetch event works today.

> I think we could get to a more targeted mechanism hung off the registration sooner, but it's definitely possible as what amounts to a short-term hack it's not worth it and we should wait for declarative routing

That's what I'm aiming to discover through my previous comment. I'm not against a focused API, but I don't want to end up creating a `doThatThingForFacebook()` API that means we later need to ship a subtly different `doThatThingForTwitter()` API.

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