[SV] The outbound and inbound relate to RtpSender and RtpReceiver objects, respectively. The local and remote candidates are actually listing attributes and do not really expose any stats. IIUC, the information contained within will be accessible from the corresponding IceCandidate object. Session should contain the sequence of peer connections, and data channels. [/SV] One problem is there are no peer connection objects in ORTC. There’s no “master” connection object. Seems to me each of the types should map 1:1 directly to the object it belongs as this enumeration doesn’t make sense for ORTC as it stands. -Robin
Received on Thursday, 12 March 2015 23:29:43 UTC