- From: Kenneth Russell <kbr@google.com>
- Date: Wed, 4 Dec 2013 09:38:40 -0800
- To: Feras Moussa <feras.moussa@hotmail.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
Looks great! Seems very well thought through. The API seems large enough that it would be worth prototyping it and writing test applications to make sure it addresses key use cases before finalizing the spec. -Ken On Wed, Dec 4, 2013 at 8:27 AM, Feras Moussa <feras.moussa@hotmail.com> wrote: > The editors of the Streams API have reached a milestone where we feel many > of the major issues that have been identified thus far are now resolved and > incorporated in the editors draft. > > The editors draft [1] has been heavily updated and reviewed the past few > weeks to address all concerns raised, including: > 1. Separation into two distinct types -ReadableByteStream and > WritableByteStream > 2. Explicit support for back pressure management > 3. Improvements to help with pipe( ) and flow-control management > 4. Updated spec text and diagrams for further clarifications > > There are still a set of bugs being tracked in bugzilla. We would like > others to please review the updated proposal, and provide any feedback they > may have (or file bugs). > > Thanks. > -Feras > > > [1] https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm
Received on Wednesday, 4 December 2013 17:39:11 UTC