- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2023 21:35:41 +0000
- To: public-webrtc-logs@w3.org
@alvestrand's request seems based on need in the https://github.com/w3c/webrtc-encoded-transform/issues/160 use case, and now that [structuredClone(value[, { transfer }])](https://html.spec.whatwg.org/multipage/structured-data.html#structured-cloning) exists in the web platform, inventing custom `frame.clone()` methods like in https://github.com/w3c/webrtc-encoded-transform/issues/161 seems wrong to me.
This would also solve whether to clone the frame buffer or not, by leaving it up to JS:
```js
const frameCopy = structuredSerialize(frame); // clones the data as well
const frameMove = structuredSerialize(frame, {transfer: [frame.data]}); // transfers the data
```
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/181#issuecomment-1595340933 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 June 2023 21:35:43 UTC