Re: [webrtc-stats] RTCPeerConnection.getStats: What to do with 'selector' argument? from jan-ivar via GitHub on 2017-02-10 (public-webrtc-logs@w3.org from February 2017)

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Fri, 10 Feb 2017 22:30:32 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-279084420-1486765830-sysbot+gh@w3.org>

E.g. selecting on a *receiver* would produce the follow stats objects:

* RTCInboundRTPStreamStats
  * RTCOutboundRTPStreamStats (associateStatsId)
  * RTCMediaStreamTrackStats (mediaTrackId)
  * RTCCodecStats (codecId)
  * RTCTransportStats (transportId)
    * RTCTransportStats (rtcpTransportStatsId)
    * RTCIceCandidatePairStats (selectedCandidatePairId)
      * RTCIceCandidateStats (localCandidateId)
      * RTCIceCandidateStats (remoteCandidateId)
    * RTCCertificateStats (localCertificateId)
    * RTCCertificateStats (remoteCertificateId)

and for a *sender* almost the same thing:

* RTCOutboundRTPStreamStats
  * RTCInboundRTPStreamStats (associateStatsId)
  * RTCMediaStreamTrackStats (mediaTrackId)
  * RTCCodecStats (codecId)
  * RTCTransportStats (transportId)
    * RTCTransportStats (rtcpTransportStatsId)
    * RTCIceCandidatePairStats (selectedCandidatePairId)
      * RTCIceCandidateStats (localCandidateId)
      * RTCIceCandidateStats (remoteCandidateId)
    * RTCCertificateStats (localCertificateId)
    * RTCCertificateStats (remoteCertificateId)

Does that look right?

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at 
https://github.com/w3c/webrtc-stats/issues/116#issuecomment-279084420 
using your GitHub account

Received on Friday, 10 February 2017 22:30:38 UTC