- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Oct 2024 07:58:59 +0000
- To: public-webrtc-logs@w3.org
> It wasn't clear from the session track definition that its feature set would be limited, which would be backwards incompatible. That's one vision of it, out of two - either (1) a normal, fully-fledged MediaStreamTrack, or (2) a reduced-feature-set MediaStreamTrack. But which is used is a secondary matter. The core offering of a session track, as I understand @tovepet here, is that it addresses your (Jan-Ivar's) expressed desire, to be able to seamlessly transition between two models (injection, switch-track). * Your models allow "switching between models at any time." * Tove's model allows "using both or either at any time, concurrently or consecutively." I believe it is objectively true, that Tove's model is more flexible. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/4#issuecomment-2406790658 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 October 2024 07:59:00 UTC