Re: [slightlyoff/ServiceWorker] ServiceWorker lifetime and respondWith() with a user-constructed ReadableStream (#882)

I guess that works as long as there is no way for js to produce a c++ stream that is really sourced from js.  For example, write to a file via a js source stream and return the file c++ stream to respondWith().  To be honest, this scares me a little.

Overall, though, I think requiring waitUntil() might be better since it covers all cases.  We don't need to add magical keep-alive logic if there is a new way to transfer a stream from js-to-c++.  We just need a note that when the extended promises settle the service worker should try to live until all js buffers enqueued in transferring streams are consumed.

---
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/882#issuecomment-209971828