- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2017 04:38:09 +0000
- To: public-webrtc-logs@w3.org
Even if "encode-decode" handles the majority of cases, it's the minority that cause complexity. What happens if you go from "decode" to "encode-decode" or vice versa? Is there a new codec object (new stats ID) or not? What happens if a payload type changes on one side for an "encode-decode" codec (I've seen this happen); does it split into two new objects (new IDs)? Also, it just feels like a cleaner object model to imagine encoders and decoders as separate entities. The codec bi-directionality is just a consequence of SDP, and I like avoiding SDP-isms when possible; it makes `getStats` more compatible with ORTC. However, if it's 2 votes against 1, I can change it, as long as we can come up with answers to the above questions. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/195#issuecomment-297609647 using your GitHub account
Received on Thursday, 27 April 2017 04:38:18 UTC