- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Sep 2022 13:52:19 +0000
- To: public-webrtc-logs@w3.org
When I wrote this spec, I thought the platform would create one codec object per configuration it supported, and let all transceivers refer to the same object. When we added transportId, that meant the objects were transport dependent; internally they should be representable as a (static object representing a supported configuration) + (dynamic object with transport ID and PT). But I don't see any reason to have multiple codec objects for the same transport. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/662#issuecomment-1235532706 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 September 2022 13:52:21 UTC