Re: [webrtc-stats] Adding "codec type" and transportId to RTCCodecStats. from Varun Singh via GitHub on 2017-04-12 (public-webrtc-logs@w3.org from April 2017)

From: Varun Singh via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Apr 2017 08:49:37 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-293514207-1491986975-sysbot+gh@w3.org>

I am wondering if the standard case is that we use the same payload type and codec for encode and decode, then we will always get two objects even though one would suffice.

I am thinking inbound and oubtbound point to codecIds, if the same codec is used for encode and decode, maybe both pointing to the same RTCCodecStats would make sense. I am on the fence on this... because in our use-case I will definitely filter and combine the codec stats if they are exactly the same.

cc: @karthikbr82

-- 
GitHub Notification of comment by vr000m
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/195#issuecomment-293514207 using your GitHub account

Received on Wednesday, 12 April 2017 08:49:44 UTC