Re: [ServiceWorker] `waitUntil()` for FetchEvent? (#584)

> Reg: TCP timeout-- it's not clear if we need to tie the lifetime of SW to the completion of async network/cache operation.

Yeah, so it sounds like it's an optimization point in the implementation rather than a constraint in the spec.

> It looks we could say that async network/cache operation that is triggered by a ServiceWorker will NOT be cancelled even after the ServiceWorker is killed (by UA), like we don't for Beacon API on page unload. (Currently the behavior of async operations upon SW termination doesn't seem to be really spec'ed?)

Yes, I think I need to add more text to make it clear. IMO, ongoing fetch can just be dropped as there's no context to process or relay the response through. And for cache operations, those responses already committed to the _request to response map_ might better be retained unless it fails. Thoughts?

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/584#issuecomment-90774504