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

Had some chat with ServiceWorker team (horo) about `.clone()` handling when ReadableStream's `read()` is used.

I think new Request/Response created by `.clone()` would have a ReadableStream and,
- data already read from the ReadableStream of the original Request/Response is not read from one of the new Request/Response
- data not read yet are mirrored to both ReadableStream regardless of whether the chunk is already queued to the ReadableStream's queue at the time of `.clone()` call or not
- `.cancel()` call on one of the ReadableStreams doesn't affect the other

Do these make sense to you?

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