Robin said: “After some thought about this issue, I think your solution of "just create a new RTCIceListener" is the right answer, plus we have enough knowledge to be able to re-use/recycle that same newly constructed RTCIceListeners for forked transports without adding another method parameter to "createAssociatedTransport(...)". The entire secondary RTCIceListener can be implicitly done in a hidden fashion. So for the ORTC API, all we need to put in the proper behaviour language for the browser engines to know what to do and for the application developer to know what to expect. Bottom line, Peter's solution will work.” [BA] createAssociatedTransport returns an RTCIceTransport. What value does transport.iceListener have in this newly created object? Does this point to an (implicitly) created iceListener object corresponding to RTCP?
Received on Wednesday, 28 May 2014 21:45:12 UTC