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

Well @bmaurer can best clarify what he meant by:

> the header CurState:XYZ where XYZ can be managed by the service worker as its cached state changes

But I read that as the last time the service worker changed something it would store the new XYZ header in some API that would then go out with the next preload.  So it doesn't have to block the preload, but its still managed by the service worker.

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