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

Unpaired candidates need to be marked as local or remote #65

Closed
alvestrand opened this issue Oct 11, 2016 · 1 comment
Closed

Unpaired candidates need to be marked as local or remote #65

alvestrand opened this issue Oct 11, 2016 · 1 comment

Comments

@alvestrand
Copy link
Contributor

At the moment, one is supposed to figure out whether a candidate is local or remote based on its position in a candidate pair.

This doesn't cover the case where you have candidates that aren't paired with anything - for instance IPv6 local candidates when talking to an IPv4-only remote system.

There should be an "isRemote = false" field on RTCIceCandidateStats, just like we have on RTCRTPStreamStats.

@alvestrand
Copy link
Contributor Author

I was wrong. Local candidates have their "type" field set to "local-candidate", while remote candidates have their "type" field set to "remote-candidate", so they're actually distinguishable. Closing issue.

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

No branches or pull requests

1 participant