News for hackers. Stuff that matters.
Re:Microsoft, Google, others Co-Author Real-Time Communicati... by McGlockenshire on Thursday August 28, 2014 @05:29PM (#8239810)
It's my understanding that ORTC was originally proposed by Microsoft as an alternative to WebRTC.

I've never been able to track down what MS thinks was actually wrong enough with WebRTC that required an alternate proposal.

Re:Microsoft, Google, others Co-Author Real-Time Communicati... by walterbell on Thursday August 28, 2014 @05:45PM (#8239880)
Found some background at http://ortc.org/History/ & http://blog.webrtc.is/2013/03/06/sdp-the-webrtc-boat-anchor/

"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. "

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.
Re:Microsoft, Google, others Co-Author Real-Time Communicati... by higherpurpose on Thursday August 28, 2014 @06:20PM (#8240062)
I don't know about the other stuff, but Microsoft hated having to use the VP8 codec instead of h.264 (even though it adopted it later on in Skype).