- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2017 09:26:09 +0000
- To: public-webrtc-logs@w3.org
The spec already contains the verbiage "An RTCMediaStreamTrackStats object represents the stats about one attachment of a MediaStreamTrack to the PeerConnection object for which one calls getStats." - this was written prior to RTPSender/RTPReceiver, and can be said to pre-shadow the concepts. The replaceTrack() operation does complicate the situation (as usual). If you do replaceTrack(), the change from track to sender will have an observable difference; the track-based stats would show the old track as "detached" and the new track as a new stats object, while a sender-based stats would change the trackIdentifier value and keep the counters increasing. A proposal I'm sure nobody will really love: *add* the sender/receiver based stats (with the splits provided in #230), and consider moving the track stats to the "obsolete" sections once we have implementation experience saying that the new objects serve the purposes better. This means that for a while, we'll report all numbers twice. Not sure if that's a Big Deal or not. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/231#issuecomment-339270357 using your GitHub account
Received on Wednesday, 25 October 2017 09:26:11 UTC