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

Clarify how icecandidatepairnominate and selectCandidatePair are to be used #184

Open
jan-ivar opened this issue Oct 31, 2023 · 0 comments
Assignees

Comments

@jan-ivar
Copy link
Member

I feel #174 merged without an explainer or example of its intended use, side-effects, or how to use it responsibly.

I've gotten some questions internally about when this API would be useful, and I couldn't immediately answer. The only situation they could think of was one where the service is operating on a particular network that it controls? Is that true? An explainer or intro or example to point at would be good.

A slide presented at TPAC says what the app can do:

Application can defer nomination of a candidate pair picked by the controlling ICE agent ...
Application can select any valid candidate pair to send data ...
Both controlling and controlled side can select a candidate pair to send data ...

But it doesn't say why or what problem is solved. The only use UDP port 3478 example given seems like it could be solved with {iceTransportPolicy: "relay"}, or by filtering icecandidate events, or am I missing something?

Application now has the responsibility & flexibility to synchronize send/receive ...

Can we lay out these responsibilities in an explainer with examples showing what's minimally needed to use the API correctly?

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