- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Jan 2019 18:30:56 +0000
- To: public-webrtc-logs@w3.org
@murillo128 @lgrahl Was just pointing out that per-data channel flow control will not completely solve the problem of side-effects from an application not keeping up on another data channel. Today implementations don't limit the message events in the event queue, and the message is considered "consumed" once it is put into the event queue, so flow control does not kick in. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457673257 using your GitHub account
Received on Friday, 25 January 2019 18:30:57 UTC