-
Notifications
You must be signed in to change notification settings - Fork 46
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
Identifier ambiguity in stat objects #350
Comments
taylor-b
added a commit
to taylor-b/webrtc-stats
that referenced
this issue
May 18, 2018
Fixes w3c#350 - RTCIceCandidateStats.transportId is the ID of an RTCTransportStats, not another RTCIceCandidateStats - RTCIceCandidatePairStats.localCandidateId and remoteCandidateId are IDs of RTCIceCandidateStats, not RTCIceCandidateAttributes (there's no such thing).
That was just a typo on my part. I'll fix it. |
vr000m
pushed a commit
that referenced
this issue
May 19, 2018
Fixes #350 - RTCIceCandidateStats.transportId is the ID of an RTCTransportStats, not another RTCIceCandidateStats - RTCIceCandidatePairStats.localCandidateId and remoteCandidateId are IDs of RTCIceCandidateStats, not RTCIceCandidateAttributes (there's no such thing).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Recently we have created a graph to have an overview how we can reach one webrtc stat object from another one (See the attachment). We used the names listed in the RTCStatsType to identify attributes in other objects pointing to another stat object. This works quite well, except (as far as I see) for transportId.
I have found that transportId points to RTCTransportStats in all appearances except in RTCIceCandidateStats where transportId points to RTCIceCandidateStats.
Is there a special reason for that, or may we ask to avoid ambiguity and came up with a better name, for an instance: candidateId?
Attachment:
webrtcStats.gv.pdf
The text was updated successfully, but these errors were encountered: