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

Re: WebRTC and backpressure (how to stop reading?)

From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Date: Thu, 27 Mar 2014 12:08:27 +0100
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <9A8CC672-3A2C-4D21-9353-FAC1ED669D5E@lurchi.franken.de>
To: Martin Thomson <martin.thomson@gmail.com>
On 27 Mar 2014, at 03:26, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 26 March 2014 14:57, Harald Alvestrand <harald@alvestrand.no> wrote:
>> In fact, you might want to read up on HTTP/2.0 - especially why it's
>> neccessary, and why it uses a single congestion-control connection between
>> each client/server pair, not multiple ones.
> 
> ...and why per-stream flow control (i.e., back pressure, which is not
> much related to congestion control) is critical to the operation of
> the protocol.
> 
> I think that we should be asking the IETF to fix SCTP for us (as
> opposed to patching its deficiences over the top).
We thought about this in the past, but it is non-trivial. This is also
one of the reasons why (in the socket API) there are no sockets per
file descriptor or you can't read from a particular stream.

So I would like to understand first what API you want and think about how to
make that work from a protocol perspective second. Simple start/stop
semantics can be realised by transferring reliably corresponding messages.

Best regards
Michael
> 
> 
Received on Thursday, 27 March 2014 13:44:52 UTC

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