- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 May 2022 19:33:14 +0000
- To: public-webrtc-logs@w3.org
My general mental model is that a method that only impacts the track should go to the track. A method that impacts the source (so all tracks) is better to keep outside of tracks. Having a single place for actions is a good simplification and will make things simpler. Having the ability to transfer a track but keep control of the capture/action manager adds flexibility to web applications, without making them any less powerful. It also seems like it will be a simpler and less error prone programmatic model for web developers. It might also be easier to implement for UA, past the boiler plate to add the probably new interface required by such a container. Overall adding this separate container looks like a nice addition, so it seems good to have a try. We should probably dive into the details to fully validate this. For instance, making it Transferable like MediaStreamTrack might be a good idea as some applications might want to delegate both track and action handling to a separate context (say a worker). But this might have impact on the corresponding API the capturer might support. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/65#issuecomment-1128056801 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 May 2022 19:33:15 UTC