Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Section 3: ICE Transport #101
From Shijun Sun:
Section 3.3. IceTransport. restart(). If this is to reset to gathering, the spec should be clear on the impact to “state”, local candidate list, etc. And, should we allow any change to the getherPolicy when restart()? And, from another perspective, can we recommend just constructing a new IceTransport as in Section 3.1, i.e. removing “restart()” from the interface?
Section 3.3. IceTransport. The icelistener should not be optional. We can’t have an empty constructor to create the iceTransport.
If gatherpolicy is not valid, gather() will throw invalid access exception.
Call gather() during gathering, throw invalid access exception.
Call gather() after gather-complete. Should UA invalidate all the local candidates reported already? Propose to throw invalid access exception unless the stop() is called explicitly.
Call start() with invalid params will throw invalid access exception
IceTransport. When “error” should be fired? What we’d like to propose: If the transport is closed without either party calling stop(), the UA should fire an error event.
Since there is no way to set the RTCIceListener after construction, I would agree that the RTCIceLIstener cannot be optional in the constructor. Should an InvalidParameter exception be thrown if invalid parameters are passed? Other suggestions seem reasonable.