-
Notifications
You must be signed in to change notification settings - Fork 44
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
How to learn nominated candidate? #527
Comments
This is an abstraction. It deliberately does not try to tell you candidates. Instead it says "send to this IP from this IP". What candidates that might correspond to is an internal detail, since you would not have declared all of them (some are dynamically discovered). Do you need to know the exact candidates? |
Currently, we are still invalidating candidates to achieve a smooth roaming of sockets that does not rely on waiting for the ICE timeout. In order to invalidate them, I need to loop over |
Alright. So if you are going down the ICE restart route. Would that change things? |
A little bit. It would still be useful to know whether I am connected via a relay candidate or not. Sending from a relay candidate requires wrapping messages in channel data messages and sending them to an entirely different socket. To learn about that, I still need to search through the list of local candidates for the one I added. I get the idea of the abstraction but I am not sure it makes much sense. If my input are candidates, then the output should maybe be as well? It is not like |
I think this is "in spirit" with the spec (see other issue): #525 (comment) |
This is a somewhat related problem to #525. Currently,
NominatedSend
event only includes the localsource
socket to send from.In case a server-reflexive candidate gets nominated, the
source
address will be set to the server-reflexive candidate'sbase
which is the same as a host candidate's address. So it is impossible to know whether the host or the server-reflexive candidate got nominated.Would it make sense to emit the two candidates instead?
The text was updated successfully, but these errors were encountered: