Re:Microsoft, Google, others Co-Author Real-Time Communicati...
by dmahugh on Friday August 29, 2014 @01:04PM
(#8243384)
You can find discussion of various aspects of ORTC's design on the public mailing list archive for the ORTC community group here: http://lists.w3.org/Archives/Public/public-ortc/. In addition to using JavaScript rather than a legacy format to configure the real-time protocols, ORTC addresses some useful real-world scenarios such as mixing and matching data connections.
- doesn’t truly solve goal of interoperability with legacy systems (eg. SIP)"
from
"the Chief Architect at Hookflash and author of the new P2P protocol, Open Peer. I used to be the CTO/ Chief Scientist at Xten, now CounterPath, and I’m the original author of the X-Lite/X-PRO/eyeBeam SIP softphone clients. "
Re:Microsoft, Google, others Co-Author Real-Time Communicati...
by tommoor on Thursday August 28, 2014 @07:32PM
(#8240318)
As someone that has spent the last 18months building on WebRTC I can agree with all of Microsofts points - particularly offer/answer state machine which is hugely problematic.
I've never been able to track down what MS thinks was actually wrong enough with WebRTC that required an alternate proposal.
"My issues with SDP can be summarized as:
- unneeded – much too high level an API
- arcane format – legacy and problematic
- offer/answer
- incompatibilities
- lack of API contact
- doesn’t truly solve goal of interoperability with legacy systems (eg. SIP)"
from
"the Chief Architect at Hookflash and author of the new P2P protocol, Open Peer. I used to be the CTO/ Chief Scientist at Xten, now CounterPath, and I’m the original author of the X-Lite/X-PRO/eyeBeam SIP softphone clients. "