“Real life is, to most men, a long second-best, a perpetual compromise between the ideal and the possible.” - Bertrand Russell
The world has indeed changed in the last year as WebRTC has made massive strides both from a standardization and from a market adoption point of view. A whole host of innovative applications are succeeding on mobile and desktop end-points.
But despite another 12 months of progress, one of the key points of contention that remained stubbornly unresolved was the great video codec debate: Should VP8 or H.264 be the Mandatory-to-Implement Video Codec for WebRTC? It was a welcome and surprising move that led the IETF Working Group to finally arrive at the following consensus just last week:
Here at TokBox we are preparing for the fifth WebRTC expo, taking place in San Jose next week from 18-20 November.
Since the last WebRTC expo in June, there has been a lot of action in the market;
For those who might not know (and are still interested in the topic?) ORTC, Object RTC, is an initiative that was started one year ago by a group of people who were not comfortable with the approach taken for the design of the WebRTC APIs. This group recently published the first official draft of an alternative API including support from very relevant people from Google and Microsoft.
In our previous post about packing more punch into the OpenTok platform we talked about a new release cadence and support policy. In order to improve our users’ experience of the OpenTok platform, we will now provide support for the current and previous versions of the client libraries.
As a quick follow up to this, we’re announcing the first set of client libraries that we will no longer be supporting.
We’re moving the OpenTok Platform to a new release cadence – less frequent with more punch. We’ve made a few significant decisions about how we’re going to release and support client updates in the OpenTok Platform, and, as these changes go live, we wanted to keep the OpenTok community properly updated.
Over the life of the OpenTok Platform, we’ve moved from weekly to bi-weekly to monthly releases. When the Platform only had web-based clients, it was possible for us and (some of) our partners to move this quickly.