W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2019

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

From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
Date: Mon, 28 Jan 2019 17:38:37 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-458228153-1548697117-sysbot+gh@w3.org>
> 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 https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-458228153 using your GitHub account
Received on Monday, 28 January 2019 17:38:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:54 UTC