- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Tue, 3 Sep 2013 10:09:41 -0700
- To: Iñaki Baz Castillo <ibc@aliax.net>
- Cc: Gustavo García <ggb@tokbox.com>, Martin Thomson <martin.thomson@skype.net>, public-orca <public-orca@w3.org>
On 2 September 2013 01:44, Iñaki Baz Castillo <ibc@aliax.net> wrote: > ok? Not really - implementing this is massively complicated. 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. Describing what actually happens during the cloning process is non-trivial, and given how much we care to support forking (i.e., we shouldn't care if forking requires a huge amount of work), I think that this is the right balance. Cloning was a complete mess in WebRTC. This API is better, but it places far too heavy a burden on the browser implementation.
Received on Tuesday, 3 September 2013 17:10:09 UTC