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 standardize Streams API to be able to handle any object. One proposal I have is - rename *ByteStream back to *Stream - add "cost" parameter to write() method of WritableByteStream - add "as-is" to ReadType then, everything should work also for arbitrary objects.
Done in ED. Now ByteStream classes have been renamed back to Stream. Binary handling features are being redesigned not to interfere generic Stream too much.
Attempted to do more clean up. - Made read() method content type agnostic - Renamed readUpTo() to readBytes() and gathered all the byte stream specific things to that method - Removed "as-is" parameter - Updated introduction texts to reflect this reorg
More reorganization done https://dvcs.w3.org/hg/streams-api/rev/79579767cc3d - Reorder properties to group generic ones and binary data specific ones - Separate binary data specific part of pipe() into pipeBytes()