WebRTC is for Losers:WebRTC是输家

时间:2022-09-22 16:11:56

该文章是引述,仅代表作者Dave Michels观点

WebRTC is for Losers

WebRTC technology has fallen short on many of its promises, including the goal of being ubiquitous, plugin-free and free.

Before explaining why WebRTC is for losers, let me be clear that I am a big fan of WebRTC. It is likely the most significant development in enterprise communications this decade. WebRTC represents the evolution both of the Web and of the Web browser, and will facilitate real-time communications as a natural feature of the Internet.

WebRTC is many things, but it is not the disruptive technology that many of us expected or that it could have been. WebRTC is a disappointment, and we, the consumers of Web technologies, will never realize its true potential. WebRTC failed to deliver, and its champions and ultimately all Web users were short-changed. As good sports, we will focus on its successes. We will celebrate being losers.

Let's be clear what WebRTC is and what it is not. It is a baseline platform that has instigated a new wave of "client-less" communications solutions. It provides an architecture that frees developers from the chores associated with licensing codecs and distributing software clients. WebRTC solutions are emerging across the industry and were spotted throughout the exhibit hall at the recent Enterprise Connect conference. These are powerful, good things.

However, WebRTC failed to deliver on three key goals which promised a revolution. WebRTC is not ubiquitous, not plugin-free, and may not even be free. WebRTC has not delivered any new capabilities and remains a niche technology with no examples that have far-reaching implications.

Starting with ubiquity, WebRTC remains relegated to the minority. A key goal of WebRTC was to raise the standard of the default browser. With such widespread support, developers could build communications-capable applications with assumed end-user compatibility. Unfortunately, this is far from reality. Compatible versions of WebRTC are supported in Chrome and Firefox only, and remain the exception for browsers on mobile devices. There is no native support on Microsoft's Internet Explorer or Apple's Safari browser.

As a result, developers must assume that end-users are not WebRTC compliant, and there's no indication of that changing anytime soon. The best use for WebRTC applications today is for internal applications where more assumptions can be made about the remote user's desktop. These same environments can easily distribute applications or plugins, so the benefit is negligible.

A quick way around ubiquity is the browser plugin. This is exactly what WebRTC promised to eliminate. Plugins extend the capability of the browser, but also represent an inconvenience and security threat. Many organizations prevent plugins from being installed. Note that not even Google's own Hangouts, which uses the VP8 codec specified in WebRTC, is supported in Chrome without a plugin.

Further, in January Google began restricting certain types of plugins on Chrome. Several plugins including Microsoft SilverLight, Facebook Video, and its own Google Talk were excepted, to minimize disruption. Without a formal standard or decision on a mandatory video codec, the plugin-free vision of WebRTC falls short.

This brings us to free. WebRTC is free today, but its legality is not. Patent claims over the VP8 codec, which is included in Chrome today, are currently in dispute. Nokia believes VP8 violates its intellectual property and has filed multiple suits, including one against HTC which calls for injunctive relief. Nokia wants to stop VP8 and has no interest or obligation to license its technologies. It is up to the courts to determine Nokia's claim of infringement, but other firms are expected to challenge VP8 as well. The future of VP8 remains uncertain, and the intellectual property issues associated with the successor VP9 are even more complex.

Cisco offered an interesting solution to the free issue by making its license of H.264 available for free. The trade-off here is it must be downloaded from Cisco, which brings us back to plugins. Cisco demonstrated WebEx running on a Chromebox using H.264 at Enterprise Connect, but this required the WebEx extension to be downloaded from Cisco.

Again, WebRTC is an important development. However, it must be understood that WebRTC is not ubiquitous, plugin-free, or free. Since codecs and applications have enabled real-time, browser-based applications for years, WebRTC is just another approach. WebRTC has not delivered any features or capabilities that are inherently new.

WebRTC is an important technology. It provides a foundation or framework for future real-time applications. It doesn't directly support current telecom technologies such as G.711 or SIP, but it could provide a Web-friendly foundation for the future. Despite its severe limitations, it seems to be sparking innovation, which may ultimately prove to be its key value.

Dave Michels is Contributing Editor and Analyst at TalkingPointz.

作者简介

Dave Michels

David Michels holds 20 years of telecom hands-on experience, starting with IVR systems to Fortune 100 operations. Currently President of Verge1 Consulting, specializing in PBX strategies for the end user and manufacturer as well as cloud services, SMB voice, channel development, unified communications, and social media. Dave has appeared at hundreds of industry trade shows, including Enterprise Connect and Interop, He publishes UC reports atwww.TalkingPointz.com, which is also the home of his PinDropSoup telecom blog. Dave contributes regularly to nojitter.com and ucstrategies.com.

The industry is in a perpetual state of change, and Dave articulates the impacts as well as identifying what matters most to clients. Dave believes the telecom industry is currently going through its most significant disruptive phase. The role of the PBX is rapidly changing, voice isn't as rigid and independent and now must deliver value in totally new interfaces. Communications are no longer voice centric, and even the notion of voice being a mission critical application doesn't resonate so clearly any more. The communications pie has more slices than ever, and how these slices interact and behave is what determines the value of unified communications.

Dave's background includes both entrepreneurial startups as well as large enterprises with international networks. Dave has served time in technical and management positions at corporations including IBM, GE, and Coors as well as multiple start-ups.

WebRTC is for Losers:WebRTC是输家的更多相关文章

  1. 《Getting Started with WebRTC》第一章 WebRTC介绍

    <Getting Started with WebRTC>第一章 WebRTC介绍 ​ 本章是对WebRTC做概念性的介绍. 阅读完本章后.你将对下面方面有一个清晰的理解:   .  什么 ...

  2. 《Getting Started with WebRTC》第二章 WebRTC技术介绍

    <Getting Started with WebRTC>第二章 WebRTC技术介绍 本章作WebRTC的技术介绍,主要讲下面的概念:   .  怎样建立P2P的通信   .  有效的信 ...

  3. 基于webrtc的视频通话时webrtc的接口调用流程

    场景: 1.A call B 2.B answer 3.A connected with B 共同的步骤: A 和 B 都需要初始化webrtc模块,创建peerconnectionfactory 步 ...

  4. WebRTC开发基础(WebRTC入门系列3:RTCDataChannel)

    除了视频和音频,webRTC还可以传输其他数据 例子: http://webrtc.github.io/samples/src/content/datachannel/datatransfer/ 应用 ...

  5. WebRTC开发基础(WebRTC入门系列2:RTCPeerConnection)

    RTCPeerConnection的作用是在浏览器之间建立数据的“点对点”(peer to peer)通信. 使用WebRTC的编解码器和协议做了大量的工作,方便了开发者,使实时通信成为可能,甚至在不 ...

  6. WebRTC开发基础(WebRTC入门系列1:getUserMedia)

    什么是WebRTC WebRTC由IETF(Internet Engineering Task Force——互联网工程任务组)和W3C(World Wide Web Consortium——万维网联 ...

  7. WebRTC 学习资源 电子书 WebRTC权威指南 Learning WebRTC

    webRTC源码下载地址:https://pan.baidu.com/s/18CjClvAuz3B9oF33ngbJIw 提取码:wl1e 1.<WebRTC权威指南>第三版 中文版 本书 ...

  8. 使用WebRTC搭建前端视频聊天室——点对点通信篇

    WebRTC给我们带来了浏览器中的视频.音频聊天体验.但个人认为,它最实用的特性莫过于DataChannel——在浏览器之间建立一个点对点的数据通道.在DataChannel之前,浏览器到浏览器的数据 ...

  9. 使用WebRTC搭建前端视频聊天室——入门篇

    http://segmentfault.com/a/1190000000436544 什么是WebRTC? 众所周知,浏览器本身不支持相互之间直接建立信道进行通信,都是通过服务器进行中转.比如现在有两 ...

随机推荐

  1. C&num; 图片的裁剪,两个图片合成一个图片

    图片的裁剪,两个图片合成一个图片(这是从网上摘的) /// <summary>         /// 图片裁剪,生成新图,保存在同一目录下,名字加_new,格式1.png  新图1_ne ...

  2. LINQ查询字符串判断是否大写

    #region Linq to 字符串char.IsUpper意思是判断是否大写            //string strDemo = "HelloWord!";       ...

  3. html&plus;css&plus;js实现标签页切换

    CSS部分: #Tab { margin:0 auto; width:640px; border:none; position:absolute; z-index:9; margin-left:320 ...

  4. 18&period;用两个栈实现队列&lbrack;2StacksToImplementQueue&rsqb;

    [题目] 某队列的声明如下:  C++ Code  123456789101112131415   template<typename T> class CQueue { public: ...

  5. mysql 日期

    数据类型 数据类型 格式 date YYYY-MM-DD datetime YYYY-MM-DD HH:MM:SS timestamp YYYY-MM-DD HH:MM:SS year YYYY 或 ...

  6. 动态规划(DP计数):HDU 5116 Everlasting L

    Matt loves letter L.A point set P is (a, b)-L if and only if there exists x, y satisfying:P = {(x, y ...

  7. Java ----------- 正则表达式(更新中。。。。。。)

    RegEx:Regular Expression. 元字符 描述 \ 将下一个字符标记符.或一个向后引用.或一个八进制转义符.例如,“\\n”匹配\n.“\n”匹配换行符.序列“\\”匹配“\”而“\ ...

  8. 在VS里面查看lua堆栈

     extern std::string get_lua_stack(void); std::string stack = get_lua_stack();    std::string get_lua ...

  9. (Problem 42)Coded triangle numbers

    The nth term of the sequence of triangle numbers is given by, tn = ½n(n+1); so the first ten triangl ...

  10. Linux IO 调度器

    Linux IO Scheduler(Linux IO 调度器) 每个块设备或者块设备的分区,都对应有自身的请求队列(request_queue),而每个请求队列都可以选择一个I/O调度器来协调所递交 ...