Re: [ortc] Ability to set priority field in RTCIceCandidate? (#42)

Changing priority (or deleting candidates) while ICE checks are ongoing seems dangerous - the peers could get out of sync. So a setRemoteCandidates call or a change to local candidates probably implies an ICE restart if checks are ongoing.

On Apr 13, 2014, at 5:19 PM, Robin Raymond <notifications@github.com<mailto:notifications@github.com>> wrote:


Is it possible to trigger code behaviour changes when a dictionary property is set? Because we need to re-prioritize ICE behaviour based upon these changes. Also I don't think it could be done as a single transaction. Do you see any issue in changing these priority attributes on the fly one-at-a-time?

—
Reply to this email directly or view it on GitHub<https://github.com/openpeer/ortc/issues/42#issuecomment-40324808>.

Received on Monday, 14 April 2014 01:13:56 UTC