- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Jan 2019 11:01:49 +0000
- To: public-webrtc-logs@w3.org
The solution proposed by @henbos would work api wise for the given problem. El sáb., 26 ene. 2019 10:31, Lennart Grahl <notifications@github.com> escribió: > 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 > <https://github.com/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. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457816843>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ABBW81cd_MFKTTQ5pzhxrmf-s9pNnMs6ks5vHCCKgaJpZM4aS7_J> > . > -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457822092 using your GitHub account
Received on Saturday, 26 January 2019 11:01:50 UTC