Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should DataChannels have a getStats() method, should they be usable as selector to the getStats algorithm? #22

Open
na-g opened this issue Apr 17, 2019 · 2 comments
Assignees

Comments

@na-g
Copy link

na-g commented Apr 17, 2019

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?

@alvestrand
Copy link
Contributor

Has anyone operating a service based on datachannels asked for stats on individual datachannels?

Unlike media, traffic on a datachannel is byte-countable at the API.

I'd like to add stats to address operational concerns with WebRTC 1.0, and leave additional functionality to use cases in the NV document if I can.

@alvestrand alvestrand transferred this issue from w3c/webrtc-pc May 9, 2019
@aboba
Copy link
Collaborator

aboba commented May 13, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants