- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2023 21:24:13 +0000
- To: public-webrtc-logs@w3.org
> The spec is using serialise with transfer as a way to copy the detach the data ownership and ensure there is no TOCTOU issue. I do not think the intent was to enable serialisation of frames. We can rewrite the spec to detach the array buffer and copy the necessary information to make things clearer. Thanks for explaining. I agree that unless the WG decides frames should be serializable, we need to rewrite that since neither RTCEncodedAudioFrame nor RTCEncodeVideoFrame contain the prerequisite [serialization](https://html.spec.whatwg.org/multipage/structured-data.html#serialization-steps) or [deserialization](https://html.spec.whatwg.org/multipage/structured-data.html#deserialization-steps) steps necessary to [have](https://w3c.github.io/webrtc-encoded-transform/#abstract-opdef-writeencodeddata) _"Let serializedFrame be [StructuredSerializeWithTransfer](https://html.spec.whatwg.org/multipage/structured-data.html#structuredserializewithtransfer)(frame, « data »)."_ and _"Let frameCopy be [StructuredDeserialize](https://html.spec.whatwg.org/multipage/structured-data.html#structureddeserialize)(serializedFrame, frame’s [relevant realm](https://html.spec.whatwg.org/multipage/webappapis.html#concept-relevant-realm))."_ work. > We can discuss making frames serialisable in parallel. To save time, can this be that issues? - If we decide NO, we do a PR with the above rewrite - If we decide YES, we do a PR with the missing (de)serialization steps, and [Serializable] in the WebIDL Does that work? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/181#issuecomment-1595333173 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:24:14 UTC