- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Sep 2023 12:54:38 +0000
- To: public-webrtc-logs@w3.org
The difference is that in the legacy mode, you only have one track that receives frames. In the new model, if each event will keep delivering frames to the old tracks too, you'd end up with an arbitrary number of "old" tracks still getting frames. This complicates things for all constituencies. * It requires care when specifying - are the tracks clones, or do they just behave like clones? How do these track interact? * It's a more delicate implementation for the UA. * It is confusing to Web developers, because they have to explicitly `stop()` the old tracks or end up with an ever-increasing number of active tracks. * Subtle bugs in the applications - forgetting to stop the old track, which does not initially yield a user-visibile effect if the track are replaced and the old ones are not connected anywhere visible - end up affecting users through increased CPU and battery consumption. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1740853200 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 September 2023 12:54:40 UTC