[转]What’s Behind Ericsson’s OpenWebRTC Project?

http://www.tuicool.com/articles/z6rAVrJ

  Ericsson’s OpenWebRTC is an alternative to Google’s codebase.

In August, Ericsson decided to officially introduce its own WebRTC stack to the world, calling it OpenWebRTC . Why is this important? Because of this minor distinction around WebRTC:

This is a slide I recently added to my collection. I finally understood that people are often unaware that WebRTC is both a standard AND an implementation of it by Google. Now there are two such open source implementations: The Google one and the Ericsson one.

Ericsson’s OpenWebRTC project offers an alternative implementation to Google’s own WebRTC implementation.

OpenWebRTC.io vs WebRTC.org

I have taken the liberty to draft the simple table below, showing the differences behind the two projects (while I have looked at and compiled Google’s WebRTC, I haven’t done it for Ericsson’s OpenWebRTC. I am relying here only on what’s written on their website).

OpenWebRTC is probably a good starting point for those planning on porting WebRTC to embedded devices or use it on a PC application. Only time will tell if this speeds up as fast as Google’s when it comes to introducing new features and capabilities.

The main two advantages it has? Support of H.264 for those who need it and the fact it isn’t thought of as a module of the Chrome browser.

The Codec Wars

When it comes to video codecs, OpenWebRTC makes a statement of being interoperable with Chrome through VP8 and being attractive to the enterprise by having H.264 supported as well.

The VP8 vs H.264 has been the debate of 2013-2014 in WebRTC. Ericsson (and Mozilla) decided to support both sides of the story, each with its own reasons.

In 2015 we will see this debate gravitate towards VP9 vs H.264 if it was up to Google, but we might end up with a VP9 vs H.265 debate – a more challenging one.

Why Ericsson?

Ericsson is a large company. This project runs at Ericsson Labs, were engineers are probably left to their own devices to tinker with technology. Some of it gets trickled back to the large mothership while the rest is kept in its distant island.

To some extent, OpenWebRTC is no different. It might be important to WebRTC, but probably won’t affect Ericsson in the short or mid term at all.

Ericsson Labs has been dealing with WebRTC since the beginning. Having open sourced their work is a logical (and brave) step. If they are able to attract developers to their code, then they get a higher sit at the table when it comes to deciding the future of WebRTC. Since Ericsson is an incumbent in communication networks, this is of value to them.

What about Bowser?

Bowser is Ericsson’s homegrown WebRTC enabled browser for iOS. They killed if off at some point and have now revived it. For me, Bowser was always about H.264 .

This has now changed, because of several things:

  1. Today, Chrome, Firefox and Opera all support WebRTC on Android (not on iOS). This wasn’t the case in the first iteration of Bowser
  2. Bowser was never a commercial browser intended for mass adoption by consumers. In the last round it was about H.264. Now it is about showcasing and manually testing OpenWebRTC – a proof of concept that the stack works

Any talks about Bowser being a new competitor to Chrome are greatly exaggerated.

Over to you

How do you see this project? The motives behind it? Its uses? Feel free to share in the comments section.

[转]What’s Behind Ericsson’s OpenWebRTC Project?的更多相关文章

  1. C10K问题渣翻译

    The C10K problem [Help save the best Linux news source on the web -- subscribe to Linux Weekly News! ...

  2. C10K问题2

    http://blog.csdn.net/zhoudaxia/article/details/12920993 是时候让 Web 服务器同时处理一万客户端了,你不觉得吗?毕竟,现在的 Web 是一个大 ...

  3. (转)The C10K problem翻译

    The C10K problem 如今的web服务器需要同时处理一万个以上的客户端了,难道不是吗?毕竟如今的网络是个big place了. 现在的计算机也很强大了,你只需要花大概$1200就可以买一个 ...

  4. WebRTC 视频对话

    今天聊一下WebRTC.很多开发者,可能会觉得有些陌生,或者直接感觉繁杂.因为WebRTC在iOS上的应用,只是编译都让人很是头痛.这些话,到此为止,以防让了解者失去信心.我们只传播正能量,再多的困难 ...

  5. 关于Socket 多线程 的一篇好文章

    http://www.kegel.com/c10k.html#topIt's time for web servers to handle ten thousand clients simultane ...

  6. 跨平台的WebRTC客户端框架:OpenWebRTC

    Webrtc的ios框架编译 http://www.th7.cn/Program/IOS/201502/390418.shtml WebRTC in WebKit : http://www.webrt ...

  7. .NET Core系列 : 2 、project.json 这葫芦里卖的什么药

    .NET Core系列 : 1..NET Core 环境搭建和命令行CLI入门 介绍了.NET Core环境,本文介绍.NET Core中最重要的一个配置文件project.json的相关内容.我们可 ...

  8. 记一个mvn奇怪错误: Archive for required library: 'D:/mvn/repos/junit/junit/3.8.1/junit-3.8.1.jar' in project 'xxx' cannot be read or is not a valid ZIP file

    我的maven 项目有一个红色感叹号, 而且Problems 存在 errors : Description Resource Path Location Type Archive for requi ...

  9. ASP.NET Core project.json imports 是什么意思?

    示例代码: "frameworks": { "netcoreapp1.0.0": { "imports" : "portable- ...

随机推荐

  1. 【Hibernate 5】继承映射配置及多态查询

    一.继承实现的三种策略 1.1,单表继承.每棵类继承树使用一个表(table per class hierarchy) -->本文主要介绍的继承策略 类继承树对应多个类,要把多个类的信息存放在一 ...

  2. postgresql安装配置

    一,什么是postgresql PostgreSQL是以加州大学伯克利分校计算机系开发的 POSTGRES 版本 4.2 为基础的对象关系型数据库管理系统(ORDBMS),简称pgsql,它支持大部分 ...

  3. iPhone 6 (iOS 9.2) extractiion failed by XRY

    My colleague extracted an iPhone 6 with XRY and it is iOS 9.2 . Unfortunately the Wizard crashed and ...

  4. hdu1171

    use fmax().-------TLE #define mmax(a,b) (a)>(b)?(a):(b);   ---796ms that's it! #include <stdio ...

  5. Javascript 常用系统内置函数

    1:在数组指定位置插入元素 array.splice(2, 0, "three");   //在索引2的位置,删除0个元素后,插入元素“three” 例子: // 原来的数组 va ...

  6. Html.ActionLink

    一 Html.ActionLink("linkText","actionName") 该重载的第一个参数是该链接要显示的文字,第二个参数是对应的控制器的方法, ...

  7. C 小复习

    C语言 signed 与 unsigned: C语言中,当表达式中存在有符号类型和无符号类型时所有的操作数都自动转换为无符号类型 signed ; unsigned ; cout << a ...

  8. Ubuntu工具:vi编辑器

    Vi简介 Vi是“Visual interface”的简称,它在Linux上的地位就仿佛Edit程序在DOS上一样.它可以执行输出.删除.查找.替换.块操作等众多文本操作,而且用户可以根据自己的需要对 ...

  9. 消息推送之GCM

    利用GCM进行消息推送 原理 1.接收端向GCM注册registerid 2.发送端发消息给GCM服务器 这个过程需要三个参数: (1)API Key (2)registerid (3)传递的数据 3 ...

  10. 软件工程 speedsnail 第二次冲刺6

    20150523 完成任务:碰撞墙壁,或线身体翻转: 遇到问题: 问题1 身体翻转与帧数冲突 解决1 运用循环嵌套解决 明日任务: 蜗牛碰到线后速度方向的调整