Re: Need to expose RTCSocket object

2013/9/2 Gustavo García <ggb@tokbox.com>:
> I'm sorry but why do you need to retrieve it later with getLocalSocket?

In the current approach, you get the local RTCSocket of a
RTCConnection, and create a new RTCConnection with same local socket.


> I'm not a big fan of supporting complex SIP forking scenarios in WebRTC, but if supporting them is a requirement it looks like if calling RTCConnection.clone() for each forking answer could be enough.

That would be a simpler approach indeed. So:


---------------------------------------
var conn = new RTCConnection(iceOptions);

// first reply arrives:

conn.connect(remote IceDescription)

// second reply arrives:

var conn2 = conn.clone();
conn2.connect(remote IceDescription2)
---------------------------------------


ok?




-- 
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Monday, 2 September 2013 08:45:11 UTC