- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 14:00:32 +0000
- To: public-webrtc-logs@w3.org
I agree that a sync setMetadata call here makes most sense, as one is only mutating local state which is later passed down into the peerconnection and handed off across threads, as Youenn described above. I put together [a proof of concept implementation](https://chromium-review.googlesource.com/c/chromium/src/+/3743422) of such an sync API in Chrome & WebRTC, just to make sure we're not missing anything and it seems to work fine. Given this, are there any remaining concerns around making the method synchronous? The RED example does seem like a good concrete instance of a class of usecases where the encoded transform drastically changes the payload such that the existing metadata no longer matches it. I've not been able to find any good way for apps to handle this without such a setMetadata() method. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/135#issuecomment-1225767936 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 August 2022 14:00:34 UTC