- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 13:06:01 +0000
- To: public-webrtc-logs@w3.org
The threading model, like for other APIs that process realtime data chunks (say web audio or web codecs), is important. This makes sure that important threading decisions are correctly discussed, described and shared with all spec users (implementors, web devs). This allows implementors to get it right more easily and reduces potential interop issues. For instance, it is unclear where maxBufferSize check is done, which can alter the API in various ways depending on the implementation. Similarly, this API currently relies on transferring WhatWG streams to workers without being blocked on the thread where streams are created. This is not straightforward from reading the spec and easy to fix in practice. All these implementation details are core to achieve behavior and efficiency. So core that it is important to have consensus on them and describe them properly. Web audio and web codecs are examples of spec that describe the model. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/27#issuecomment-852108469 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 13:06:18 UTC