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.

Sign up for GitHub

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

Jump to bottom

No way to tell what transport is associated with an RTCIceCandidateStats #92

Closed
taylor-b opened this issue Dec 6, 2016 · 0 comments
Closed

No way to tell what transport is associated with an RTCIceCandidateStats #92

taylor-b opened this issue Dec 6, 2016 · 0 comments

Comments

@taylor-b
Copy link
Contributor

taylor-b commented Dec 6, 2016

If the RTCIceCandidateStats is referenced by an RTCIceCandidatePairStats, it's possible to tell. But not every candidate will be paired (for instance, before any remote candidates have been trickled).

I propose adding a DOMString transportId just like we have on RTCIceCandidatePairStats.
taylor-b added a commit to taylor-b/webrtc-stats that referenced this issue Dec 6, 2016
@taylor-b
Add transportId to RTCIceCandidateStats.
b45d868 
Needed to associate a candidate with a transport in case the candidate
is not paired.

Fixes issue w3c#92.
@taylor-b taylor-b mentioned this issue Dec 6, 2016
Merged
@vr000m vr000m mentioned this issue Dec 12, 2016
Closed
taylor-b added a commit to taylor-b/webrtc-stats that referenced this issue Dec 12, 2016
@taylor-b
Add transportId to RTCIceCandidateStats.
a1f0d5f 
Needed to associate a candidate with a transport in case the candidate
is not paired.

Fixes issue w3c#92.
@vr000m vr000m closed this as completed Dec 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vr000m @taylor-b