2013/9/3 Robin Raymond <robin@hookflash.com> > For forking conditions, we can reuse the same RTCSocket object with two > connections, each object becomes distinct but uses the same physical port > and local ice information. Everything else is unique (and should be). This has been implemented: https://github.com/openpeer/ortc/blob/master/draft-w3c-ortc-api-00.md#interface-definition https://github.com/openpeer/ortc/blob/master/draft-w3c-ortc-api-00.md#getlocalsocket https://github.com/openpeer/ortc/blob/master/draft-w3c-ortc-api-00.md#the-rtcsocket-class > So why is clone needed? I don't think it's desirable to auto-clone media > track settings for example from one object to another. Well, this can probably be implemented at JS level, but typically in a SIP forking case you want to keep same media tracks and tracks settings for all the legs. -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Tuesday, 3 September 2013 20:11:26 UTC