This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23977 - [Streams API] Generic object stream
Summary: [Streams API] Generic object stream
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Streams API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Takeshi Yoshino
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2013-12-03 16:46 UTC by Takeshi Yoshino
Modified: 2014-02-03 09:04 UTC (History)
2 users (show)

See Also:


Description Takeshi Yoshino 2013-12-03 16:46:47 UTC
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.
Comment 1 Takeshi Yoshino 2014-01-28 05:31:19 UTC
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.
Comment 2 Takeshi Yoshino 2014-01-31 04:11:10 UTC
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
Comment 3 Takeshi Yoshino 2014-02-03 09:04:32 UTC
More reorganization done
- Reorder properties to group generic ones and binary data specific ones
- Separate binary data specific part of pipe() into pipeBytes()