Re: Thoughts behind the Streams API ED

On Tue, Nov 12, 2013 at 5:23 PM, Aymeric Vitte <vitteaymeric@gmail.com>wrote:

>  No, see my previous reply, unless I am proven incorrect, I still think we
> should have:
>
> - pause/unpause
> - stop/(implicit resume)
>
> Regards,
>
> Aymeric
>
> Le 11/11/2013 22:06, Takeshi Yoshino a écrit :
>
>  Aymeric,
>
>  Re: pause()/resume(),
>
>
Sorry. This is typo. I meant pause()/unpause().


>
>  I've moved flow control functionality for non-exact read() method to a
> separate attribute pullAmount [1] [2]. pullAmount limits the max size of
> data to be read by read() method. Currently the pipe() method is specified
> not to respect pullAmount but we can choose to have it to respect
> pullAmount, i.e. pausing pipe()'s transfer when pullAmount is set to 0.
> Does this work for your use case?
>
>  [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23790
> [2] https://dvcs.w3.org/hg/streams-api/rev/8a7f99536516
>
>
> --
> Peersm : http://www.peersm.com
> node-Tor : https://www.github.com/Ayms/node-Tor
> GitHub : https://www.github.com/Ayms
>
>