- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 May 2021 11:57:35 +0000
- To: public-webrtc-logs@w3.org
> The use case I use as an example is https://webrtc.github.io/samples/src/content/insertable-streams/video-analyzer/, where the whole point of the processing is to get data that is presented on the page by code running on the main thread. I have not looked precisely at what this page is doing but I think the usecase can be defined as: - Do the video rtc pipeline as efficiently as possible (as usual). In addition, analyse the data to gather stats/monitor the pipeline - Show the stats/analyze results in the web page I would implement it as: - Use script transform to efficiently do the processing out of main thread. Gather the stats in the worker. - Send the stats back to the page. Based on that, the current API supports that use case and would lead to more optimal results than doing the whole processing in main thread. > MessagePort in Blink is implemented as a Mojo IPC operation In the previous message, I was referring to Worker.postMessage, not WorkerGlobalScope.postMessage (which might be the same for shared worker, service worker and dedicated worker in Chrome). In any case, allowing a MessagePort would lead to require Mojo IPC operations. Currently, RTCRtpScriptTransform only requires posting a task on the worker thread, which is much simpler to implement. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/89#issuecomment-844032077 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 May 2021 11:57:49 UTC