- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Jan 2019 13:59:20 +0000
- To: public-webrtc-logs@w3.org
If you empty the receive buffer and put it in a temporary message buffer then you can receive messages larger than the receive buffer, but having another buffer does not solve the congestion control problem. Eventually, the temporary message buffer will fill up and then either 1) you stop emptying the receive buffer to get congestion control to kick in, which is a variety of the existing proposal, or you 2) create more message buffers, in which case we have the same problem that we do now (it's just that the buffer is stored in "message buffers" instead of in in-queue PostTasks). If we are CPU-bound we have to have some sort of congestion control. Blocking messages from arriving sounds like a less severe problem than resource exhaustion. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-458142021 using your GitHub account
Received on Monday, 28 January 2019 13:59:22 UTC