Re: [ServiceWorker] Backpressure on fetch integrated with Streams (#452)

I would think in all these cases conceptually what is happening is that the stream is being locked-then-consumed while it is copied over into the new request, or fed to the network, or put into the cache. "waiting" while being consumed, then "closed" after it's done being consumed, makes the most sense to me.

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