You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it stands if one wants to check the stats of a RTCDataChannel one needs to poll the stats of the entire RTCPeerConnection. Does it make sense to allow RTCDataChannel stats to be accessed directly like RTCRtpSenders and RTCRtpReceivers via a getStats() method? Does that also imply that RTCDataChannels should be accepted as a selector for the getStats() algorithm?
The text was updated successfully, but these errors were encountered:
In ORTC, the RTCSctpTransport has stats associated with it, but not the RTCDataChannel object. For ORTC, this seems like an oversight. But the benefit of adding support for this in WebRTC 1.0 seems slim.
As it stands if one wants to check the stats of a
RTCDataChannel
one needs to poll the stats of the entireRTCPeerConnection
. Does it make sense to allowRTCDataChannel
stats to be accessed directly likeRTCRtpSender
s andRTCRtpReceiver
s via agetStats()
method? Does that also imply thatRTCDataChannel
s should be accepted as a selector for thegetStats()
algorithm?The text was updated successfully, but these errors were encountered: