- From: Martin Thomson <martin.thomson@skype.net>
- Date: Tue, 3 Sep 2013 17:17:07 +0000
- To: Iñaki Baz Castillo <ibc@aliax.net>, Martin Thomson <martin.thomson@gmail.com>
- CC: Gustavo García <ggb@tokbox.com>, public-orca <public-orca@w3.org>
> -----Original Message----- > From: Iñaki Baz Castillo [mailto:ibc@aliax.net] > Sent: Tuesday, 3 September, 2013 10:15 > To: Martin Thomson > Cc: Gustavo García; Martin Thomson; public-orca > Subject: Re: Need to expose RTCSocket object > > 2013/9/3 Martin Thomson <martin.thomson@gmail.com>: > > The alternative is actually fairly straightforward: > > > > var conn = new RTCConnection(...); > > // ...send offers... > > // first answer > > conn.addRemoteCandidate(...); > > // second answer > > var conn2 = new RTCConnection(conn.localSocket, ...); > > conn2.addRemoteCandidate(...); > > > > > > It's not significantly different, or even much harder. Except that > > you don't have to worry about the state of the first connection. > > The problem above is that you must enter again the full list of media streams > (and maybe customized settings per RTCTrack, along with DTMF > stuff) in the second RTCConnection. That was the main purpose of the > clone() method: to clone the RTCTrack instances within the connection. [MT] I'd consider that a feature, not a bug.
Received on Tuesday, 3 September 2013 17:21:23 UTC