This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
To bridge existing unstoppable APIs such as WebSocket to the Stream style APIs, we need to buffer write requests. We can address this by e.g.: - allowing multiple write()s without waiting for completion. maybe by having a queue inside a Stream - using infinite size Stream Figure out which is the best thing to do.
Done in preview ver https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html Multiple write()s are allowed. Producer code can issue write()s sequentially and synchronously.
Preview ver merged into ED