Re: [streams] Custom tee function (#401)

>> If one reader is 1 gigabyte ahead of the other, do you exert back pressure?

>This is really the crux of the problem and AFAICT not optimizable in the general js case.

The point is that it is not generally optimizable, but that there were cases where massive state commitment could be avoided.  If, for example, you could quite reasonably produce the same stream again, then you could implement `tee()` by producing two different streams that happen to have the same content.


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