W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2016

[webrtc-pc] Unclear how the `getStats` track selector works in the context of RtpSenders.

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Apr 2016 17:46:27 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-146993355-1460137586-sysbot+gh@w3.org>
taylor-b has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Unclear how the `getStats` track selector works in the context of 
RtpSenders. ==
Suppose you have an `RtpSender` sending track `A`. It send 100 packets
 with this track.

Then you call `sender.replaceTrack(B)`, and the sender sends 200 
packets from the new track.

Now, if you call `pc.getStats(A)`, what happens? The spec says:

> For a track to be a valid selector, it must be a MediaStreamTrack 
that is sent or received by the RTCPeerConnection object on which the 
stats request was issued.

So is the promise resolved with an error, since track `A` is no longer
 being sent?

Conversely, if you call `pc.getStats(B)`, do you see stats from only 
the period when the sender was sending track `B` (`packetsSent` is 
200), or from the entire history of the sender (`packetsSent` is 300)?

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/572 using your GitHub account
Received on Friday, 8 April 2016 17:46:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:48 UTC