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

Queueing of candidate events #152

Closed
aboba opened this issue Sep 27, 2014 · 2 comments
Closed

Queueing of candidate events #152

aboba opened this issue Sep 27, 2014 · 2 comments

Comments

@aboba
Copy link
Contributor

aboba commented Sep 27, 2014

Currently the document does not specify what happens between when an RTCIceGatherer object is created, and when an onlocalcandidate event handler is provided. Presumably the RTCIceGatherer begins gathering once created and queues candidate events until an onlocalcandidate event handler is assigned, correct?
@ibc
Copy link
Contributor

ibc commented Sep 27, 2014

Makes sense. It should buffer all the candidates and fire events when the handler is provided.

@aboba
Copy link
Contributor Author

aboba commented Sep 30, 2014

Proposed text for Section 5.3.1 is as follows:

onlocalcandidate of type EventHandler, , nullable
This event handler, of event handler event type icecandidate, must be supported by all objects implementing the RTCIceGatherer interface. It receives events when a new local ICE candidate is available. Since ICE candidate gathering begins once an RTCIceGatherer object is created, candidate events are queued until an onlocalcandidate event handler is assigned.

@aboba aboba closed this as completed Oct 10, 2014
robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Oct 14, 2014
Address questions about RTCDtlsTransport.start(), as noted in: Issue w…
7a48e0b 
…3c#146

Address questions about RTCRtpCodecCapability.preferredPayloadType, as noted in: Issue w3c#147
Address questions about RTCRtpSender.setTrack() error handling, as noted in: Issue w3c#148
Partially address 'automatic' use of scalable video coding (in RTCRtpReceiver.receive()) as noted in: Issue w3c#149
Renamed RTCIceListener to RTCIceGatherer as noted in: Issue w3c#150
Added text on multiplexing of STUN, TURN, DTLS and RTP/RTCP, as noted in: Issue w3c#151
Address issue with queueing of candidate events within the RTCIceGatherer, as noted in: Issue w3c#152
Clarify behavior of RTCRtpReceiver.getCapabilities(kind), as noted in: Issue w3c#153
@robin-raymond robin-raymond mentioned this issue Oct 14, 2014
Merged
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
@ibc @aboba