W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2012

When to fire onicecallback

From: Li Li <Li.NJ.Li@huawei.com>
Date: Fri, 13 Jul 2012 16:13:05 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <B60F8F444AAC9C49A9EF0D12D05E0942216AF2F0@szxeml535-mbx.china.huawei.com>
In [1], the statement:

onicecandidate of type Function, nullable
This event handler, of event handler event type onicecandidate<http://dev.w3.org/2011/webrtc/editor/webrtc.html#event-onicecandidate> , must be supported by all objects implementing the PeerConnection<http://dev.w3.org/2011/webrtc/editor/webrtc.html#idl-def-PeerConnection> interface. It is called any time there is a new ICE candiate can be added to the a previos offer or answer.

implies that onicecandidate() can only be called after: 1) first createOffer() on the caller; or 2) first createAnswer() for the callee. Is this true? If so, we need to make it clear in the spec.

Do we also allow ICE candidates to be generated (and sent) for the callee prior to the first createAnswer()? If so, we should say the function can be called after the first setRemoteDescription("offer", SDP) or createAnswer().

Received on Friday, 13 July 2012 16:17:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:30 UTC