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

> One thing is competition, and another one is causing unneeded retransmisión.

Fair enough. But like I said, it's a workaround.

> I was only referring to the receiving side (sender can be a server with proper streaming api implemented).

I think we're talking about two different things.

> Ok, so if we instead of causing a deadlock, we document that in case that the `a_wnd` is exhausted and the browser has no completed messages to deliver to the api, then it will close the datachannel/discard the current messages/close pc, would it be ok then?

No, of course that's not acceptable.

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

Received on Monday, 28 January 2019 17:38:39 UTC