Re: [webrtc-stats] Should track also contain RTCRtpReciever stats? from henbos via GitHub on 2018-09-06 (public-webrtc-logs@w3.org from September 2018)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 Sep 2018 15:26:57 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-419137097-1536247615-sysbot+gh@w3.org>

Yes that sounds like a good idea to me.
Other uses of "trackId" that should move to the obsolete section: RTCInboundRtpStreamStats.trackId, RTCOutboundRtpStreamStats.trackId.

If we still want to expose stream identifiers that more properly belongs to the sender and receiver state as a sequence&lt;DOMString&gt; streamIdentifiers. The webrtc-pc spec has shied away from streams for a while now so these might not be very interesting but that would be the right way to do it.


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

Received on Thursday, 6 September 2018 15:26:59 UTC