ORTC and the Future of WebRTC
The first stable ORTC (Object RTC) specification is out. The questions is how is it going to impact WebRTC?
- unneeded – much too high level an API
- arcane format – legacy and problematic
- lack of API contact
- doesn’t truly solve goal of compatibility to legacy systems
In the following months others joined him and the W3C Object RTC (ORTC) Community Group was formed to define “a set of ECMAScript APIs in WebIDL to allow media to be sent and received from another browser or device”. The group currently has 60 members including Microsoft and Google, and has produced the first stable specification draft: Object RTC (ORTC) API for WebRTC.
Doug Mahugh (Microsoft) considers that ORTC is now “complete enough for implementations to gain experience with it, so that a ‘call for implementations’ will go out.” He outlines some of the reasons why ORTC is useful:
Also, the ORTC FAQ provides more reasons for a new web communication specification:
Now that Microsoft and Google are pushing ORTC, one might wonder what will happen to WebRTC? Since several browser makers – Google, Mozilla, Opera, Microsoft - have already invested a lot in supporting WebRTC they are not going to dump it but rather adapt it to support ORTC. According to Justin Uberti (Google), WebRTC 1.1 will integrate ORTC (see video @ 29m20s). So, developers won’t have to rewrite their RTC applications but they are encouraged to transition towards using the ORTC API which is a more natural one to use in the browser.
According to Uberti and Serge Lachappelle (Google), some 450 companies have developed WebRTC apps so far, and there are ~1.7B devices supporting it (video @ 43m40s), the number being supposed to grow to 4B by 2018 considering that WebRTC is to be used for video chat, voice calling, file sharing in all sorts of devices, a Google team demonstrating a rover with a 3D camera operated over WebRTC (video @ 2m36s).
Caitie McCaffrey Apr 24, 2015