- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Jan 2019 09:31:55 +0000
- To: public-webrtc-logs@w3.org
> an API for delivering data to the app as soon as it is received on the sctp chunks, ndata for interleaving and the change to the a_rnwd handling would solve all the issues. Even if we had all of that I'd disagree. The receive buffer is message and stream agnostic. As long as streams are sharing this buffer, one stream not being read from would eventually bring all other streams to a standstill. We can happily discuss that further but I think we're slowly drifting off-topic. IIRC the original question of @henbos kind of went into the direction whether there is an easy fix for the current 1.0 API... and at this point I don't think there is one. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457816843 using your GitHub account
Received on Saturday, 26 January 2019 09:31:57 UTC