This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There're requests to make it able to mirror a byte stream to multiple destinations. Currently, it's addressed by pipe(Stream[]) but it involves memory copy. Rather than that, we could choose to make ReadableByteStream clonable. fork() creates another ReadableByteStream instance that refers to the same internal data source as the original ReadableByteStream. Implementation of the original ReadableByteStream may choose to have range reference counting to control lifetime of the original data source sequence. Each ReadableByteStream works like "reading cursors" for the original data source. Since the internal data source sequence is not drained until all the cursors are done, a slow consumer can block fast ones. If you don't want to block the faster consumers, you can choose to insert a ByteStream to buffer data for the slow consumer while keep draining data from the original data source quickly. ---- We haven't done enough study about necessity of pipe(). pull/push strategy of pipe() should also be well researched.
Check out ServiceWorker's use case. https://github.com/slightlyoff/ServiceWorker
Added a section describing decoupling of data source and ReadableByteStream. https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html This would help implementing substream() method.
We can start with fork() feature without size. (we call fork() with size as "substream()"). When there's request for substream(), let's add.
fork() done in preview ver https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html Strategy option (explained in the first post) not done.