Recurrently, people are arguing on different webrtc mailing lists or social sites. Some questions are still left open: which MCU/SFU is better, which PaaS is better, should one work on webRTC in Safari? in Edge? Usually some kind of statistics is being used. While it is well known that you can make statistics say whatever you want them to, I do not always see reason to argue. Indeed, most of the time people argue about different use cases that are not opposed to each other, or implicitly define different scopes that do not overlap. I thought it would be good to clarify things a little bit by presenting several trustable source of data for browser usage, webrtc support, and define a view usual use cases for illustration.
Continue reading
Month: December 2016
Webrtc in Safari Update – Q4 2016
Apple was represented by a dozen of employees at the W3C TPAC in September. The fact that it was held in sunny Lisbon late September might explain the surge in interest, in any case we were very happy to have them with us. I usually try to meet with the WebRTC team once a quarter, and we took this opportunity to go over the latest Q4 news that can be made public. Toward the end of the post, I will also give away some of my tricks to monitor public WebRTC activity in webkit.
Overview of WebRTC Media Servers
This is a translated, adapted version of an original post by NTT’s Iwase Yoshimasa available here, with agreement from the author. As the ecosystem move quickly, some updates were added in blue and in italic.
This post describes the current state (as of september 2016) of MCU and SFU media servers used in WebRTC solutions. I hope it will serve as a quick reference for those wanting to know more about the concepts and the available projects. The details of each product introduced here are not provided, but a link to each product is, so you can read further if you want. Moreover, we almost only mention stand alone media servers, and did not touch on webRTC CPaas or PaaS.