Because ORTC doesn't have transceivers, both the sender and receiver have a kind attribute. So if a WebRTC 1.0 implementation is built on top of ORTC (either natively or via a shim), kind would be available in the sender and receiver. However, WebRTC 1.0 implementations are not required to support ORTC, and in WebRTC 1.0 sender.kind and receiver.kind would need to be the same as transceiver.kind. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1765#issuecomment-364628154 using your GitHub accountReceived on Saturday, 10 February 2018 05:41:17 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC