- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 May 2020 10:09:19 +0000
- To: public-webrtc-logs@w3.org
Given the use case, this API might better fit with insertable streams. To reduce race issues, this API should be tied as close as possible to the encoder, the ReadableStream being the closest we have. > Do we need a requestKeyFrame on the receiver? Mainly to handle decrypt errors. Seems to make sense, for metadata as well in theory. That is a bit more tricky since this API is trying to influence the encoder of the other side, communication channel being potentially lossy. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-629151571 using your GitHub account
Received on Friday, 15 May 2020 10:09:21 UTC