- From: nisse-work via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2022 07:44:56 +0000
- To: public-webrtc-logs@w3.org
> Implementing setMetadata requires going deep into the webrtc stack and deal with a number of objects living in different threads. Might be doable synchronously (as getMetadata is), but it would be prudent to try to sketch an implementation before committing to a sync interface. I had a quick look at the webrtc implementation of getMetadata, and it appears to return a reference to internal state, and it appeared to make the assumption that it's immutable (and then I suppose chromium makes a copy when packaging it for js access). Making it mutable and properly synchronized looked a bit tricky at first look. So maybe we shouldn't require synchronous operation. -- GitHub Notification of comment by nisse-work Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/135#issuecomment-1162764392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 June 2022 07:44:58 UTC