News for hackers. Stuff that matters.
Re:Status IE – IE's feature status and plans by dstorey on Wednesday April 02, 2014 @09:11PM (#7520224)
Object RTC is developed by a community group at the W3C. It includes people from Google, Microsoft and a number of telecom companies, amongst others http://www.w3.org/community/ortc/
Re:Status IE – IE's feature status and plans by alfet on Wednesday April 02, 2014 @09:42PM (#7520367)
so whats the difference between the two? its the first time i hear about object RTC.
Re:Status IE – IE's feature status and plans by elisee on Wednesday April 02, 2014 @09:52PM (#7520419)
Microsoft had a competing proposal to WebRTC called CU-RTC-Web which, as far as I understand it, proposed to get rid of the Session Description Protocol (which is text-based and thus difficult to parse/edit) and provide lower-level APIs instead (details here: http://www.tokbox.com/blog/what-the-cu-rtc-web-vs-webrtc-deb...).

I've just started reading up on ObjectRTC but I believe it plans to offer an API to replace SDP too and Microsoft has moved to it since it's similar to their CU-RTC-Web proposal. All in all, it looks like this will delay the adoption of WebRTC everywhere but will be for the best in terms of API and developer experience in the end.

Re:Status IE – IE's feature status and plans by fishy929 on Thursday April 03, 2014 @02:29AM (#7521277)
> which is text-based and thus difficult to parse/edit

That's not what I normally conclude when I think "text-based."

Re:Status IE – IE's feature status and plans by tkmcc on Thursday April 03, 2014 @02:35AM (#7521293)
I think he means programmatically :).
Re:Status IE – IE's feature status and plans by amaks on Thursday April 03, 2014 @12:45AM (#7521005)
"Lowe level API instead" suspiciously sounds like a lock in tactic for a platform specific stuff (read Windows).
Re:Status IE – IE's feature status and plans by orf on Thursday April 03, 2014 @02:31AM (#7521284)
No it doesnt
Re:Status IE – IE's feature status and plans by nairteashop on Wednesday April 02, 2014 @09:55PM (#7520426)
It's a nicer javascript object based API for interacting with WebRTC. WebRTC by default uses an SDP offer/answer based approach.

Here is a more detailed rationale for this API: http://tools.ietf.org/id/draft-raymond-rtcweb-webrtc-js-obj-...