Re: Request for feedback: Streams API

Thanks. ByteStream is already partially implemented in Blink/Chromium. As
one of implementors, I'll continue prototyping and share issues here.

I haven't got time for, but writing some polyfill might be also good thing
to do.

Takeshi


On Thu, Dec 5, 2013 at 2:38 AM, Kenneth Russell <kbr@google.com> wrote:

> 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
>
>