W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2014

Re: WebRTC and backpressure (how to stop reading? And how to start sending again?)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 07 Apr 2014 10:28:38 +0200
Message-ID: <534261B6.9060602@alvestrand.no>
To: public-webrtc@w3.org
On 03/27/2014 09:11 AM, Aymeric Vitte wrote:
> It's here https://github.com/whatwg/streams
> It's a "merge" of WHATWG/W3C Streams specs taking large inspiration of 
> node's streams.
> There are still some open questions but I think all groups related to 
> streams should start integrating this from now.

"Soon to become a Living Standard" .... I think this seems just a little 
bit unstable. And missing enough data to be completely unimplementable.

I also note some grand bloopers, like this one:

> Push sourcespush data at you, whether or not you are listening for it. 
> They may also provide a mechanism for pausing and resuming the flow of 
> data. An example push source is a TCP socket, where data is constantly 
> being pushed from the OS level, at a rate that can be controlled by 
> changing the TCP window size.

Eh.... no. The rate of data flow cannot be controlled by changing the 
TCP window size. Completely different concept.

I hope the Streams discussions converge on an usable spec at one point 
in time, but I don't think the WebRTC WG can take anything useful from 
the spec at that particular URL at this particular time.

(Note: I tried to read the stuff at


since that was what the URL you gave me pointed to as "the current spec".)

Received on Monday, 7 April 2014 08:29:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:38 UTC