- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Jan 2017 09:15:32 +0000
- To: public-webrtc-logs@w3.org
I like this idea. Supposedly the caller cares about a track and all of its attachments and this gives that, per-attachment track stats. It also means that the change to the spec and implementations are minor since the dictionary does not have to change. Whether or not we want RTP sender/receiver stats I don't think that can cover per-track stats since a sender can change which track it is using and that could happen in-between calls to getStats and track stats accumulate over time. Even if possible that sounds like a really big hassle for a caller interested in tracks. @jan-ivar The RTCMediaStreamTrackStats.trackIdentifier[1] will have the value of MediaStreamTrack.id[2]. If we have one RTCMediaStreamTrackStats per attachment, the multiple attachment case would mean multiple stats objects have the same trackIdentifier. [1] http://rawgit.com/w3c/webrtc-stats/master/webrtc-stats.html#dom-rtcmediastreamtrackstats-trackidentifier [2] https://www.w3.org/TR/mediacapture-streams/#widl-MediaStreamTrack-id -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/130#issuecomment-271238251 using your GitHub account
Received on Monday, 9 January 2017 09:15:49 UTC