Re: [streams] Define "tee"ing a stream (#271)

Understood.  I agree that pure js stream behavior need to be exactly defined.

In the fetch Request/Response clone() case, gecko uses "infinite" buffer size already to match XHR behavior of not doing any back pressure to the network.  So this won't come into play for us there.

I understand blink does do back pressure for fetch(), but I don't know how blink's Request/Response clone() works.  Back pressure on peer streams might be an issue there.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/271#issuecomment-74900423