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: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
Date: Mon, 28 Jan 2019 16:33:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-458202708-1548693181-sysbot+gh@w3.org>
> It would be an abuse of the receive buffer to work around an API issue. 

Datachannel API is not well suited for SCTP, that's why we are here, so yes, we are already abusing it. 

> And it would break once someone activates ndata (which is a spec requirement).

That's true, but that's also true that when someone activates ndata and try to send 10 4GB files with current API (common torrent case), it will not work either with current API.

> Needless to say that transport protocol implementations usually allocate the buffer at once...

That's an implementation issue.

GitHub Notification of comment by murillo128
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-458202708 using your GitHub account
Received on Monday, 28 January 2019 16:33:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:10 UTC