Re: Thoughts behind the Streams API ED

OK, thanks, let's see what happens...

Regards

Aymeric

Le 12/11/2013 09:54, Takeshi Yoshino a écrit :
> On Tue, Nov 12, 2013 at 5:20 PM, Aymeric Vitte <vitteaymeric@gmail.com 
> <mailto:vitteaymeric@gmail.com>> wrote:
>
>     Takeshi,
>
>     See discussion here too: https://github.com/whatwg/streams/issues/33
>
>     The problem with stop again is that I need to handle myself the
>     clone operations, the advantage of stop-eof is:
>
>     - clone the operation
>     - close it
>     - restart from the clone
>
>     And as I mentioned before this would work for any operation that
>     has unresolved bytes (TextDecoder, etc) without the need of
>     modifying the operation API for explicit clones or options.
>
>
> OK. I understood your needs.
>
> As explained in the previous mail, if we decide to take in your 
> suggestion, I'd implement your stop-eof as a more generic in-band 
> control signal. In other words, changing the draft to propose message 
> stream than byte stream.
>
> I estimate that this feature sophisticates implementation much. So, I 
> want to hear more support and justification.
>
> For now, I filed a bug to track discussion. 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23799

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

Received on Tuesday, 12 November 2013 13:02:35 UTC