Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086)

BTW regarding backpressure, couldn't this be done by the app itself sending
back an "ack" messages in another datachannel? Don't think we need an API
and protocol change for that.

El vie., 25 ene. 2019 16:23, Lennart Grahl <>

> This could be a slight improvement for WebSockets but it would not work
> for SCTP-based data channels. SCTP has only one receive buffer per
> association. Thus, you would risk that one data channel *filling up* (for
> example a low priority file transfer or, even worse, a channel that is
> being completely ignored and never bound by the application) blocks
> receiving messages from another data channel (for example real-time sensor
> data).
> Furthermore, doing this on a message-based level is insufficient since
> messages can be of arbitrary size (although Chrome refuses to accept that
> messages can be larger than 64 KiB 😛). If one side sends a 10 MiB
> message then you still have to buffer 10 MiB. The same applies to 100 MiB,
> and so on. That breaks the backpressure mechanism.
> So, we not only need an API that allows to receive parts of a message (
> #1732 <>) but also find a
> solution for the *one receive buffer per association* problem which
> requires some protocol work. I have some ideas how it could be done by
> using PPIDs to signal backpressure.
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <>, or mute
> the thread
> <>
> .

GitHub Notification of comment by murillo128
Please view or discuss this issue at using your GitHub account

Received on Friday, 25 January 2019 16:04:31 UTC