Re: [ServiceWorker] Background caching (#574)

Oh right... backgroundPut() is a put().  Sorry.

I think it might work for put() as well as long as the child tab process stays alive.  (Its unfortunate, but in the fetch()+put() case we route all the body data through the child process.)

I guess from a spec point of view, though, it seems content script is no longer involved after cache.put() if the promise is ignored.  So as long as the browser is not shutdown, then the put() should complete regardless of what content script does.

At least that was my reading of the spec.  Maybe we should clarify this case as cancelling the put when the worker dies would make the SW lifecycle observable to content through cache inspection.

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