Signaling between client end points has always been an important facet for most interactive web applications. The use cases range from text chatting to multiplayer games to driving a robot remotely. In the world of HTML5, most developers establish signaling through websockets, long polling and server side events. However with the advent of WebRTC, data channels joined the ranks and the question posed by many developers is “Where do data channels fit in the equation?”
Data Channels provide a way to send binary / text data to another peer over the browser. The data channel api is very similar to web sockets when it comes to sending different types of data. It works peer to peer without the need of a centralized server or an additional hop in most cases.
When creating new services and products, organizations always face a challenge whether to buy or build key underlying components and functionality. As WebRTC attracts an increasing degree of interest, we regularly hear from customers that they are considering the trade-off around the decision to buy or build. Many go so far as to try and build their own real time video or audio solution before they turn to a hosted platform like OpenTok. Not surprisingly given the business we are in, we come down pretty strongly on the side of leveraging a hosted service.
Come November, it will have been four years since we launched the OpenTok platform into the world. Can you believe it? During that time technology has evolved, market demands have shifted, and mobile has become king. As your ambassador to real-time communications, we’ve stayed on top of that ever-changing ecosystem.
That’s why we have some important news to share with you – The OpenTok 1.0 platform will no longer be supported as of January 5th, 2015. It was a hard decision to make as the TokBox team and you – the OpenTok community – have dedicated so much time and energy to building on top of it.
WebRTC is changing the way enterprises communicate within their organization and with their customers.
As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.
SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.
While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.
Hot off the heels of our OpenTok 2.0 Archiving API pricing and storage announcement we’re excited to announce that our Archiving API has now gone into production.
You can find out more about the features of this API in our previous post or by taking a look at our docs page and here is a quick summary just in case.
Following on from our OpenTok archiving and storage announcement we’re excited to fill you in on some updates we are making to our OpenTok iOS and Android SDKs 2.2 that are going into production. What started out as internal engineering project has paved the way to the release of a suite of valuable mobile features which have become a formal part of the product offering, setting OpenTok further apart from other WebRTC platforms.
OpenTok Mobile SDKs, Revision 2: The Video Driver
In the latest versions of the OpenTok SDKs for iOS and Android, everything is new. We found an opportunity to learn from the lessons of the past two years, and seized it to conduct an overhaul of the architecture of the client. The 2.2.0 release of the iOS and Android SDKs marks the second major revision of the implementation of the OpenTok Mobile SDKs. This post highlights one of the many new features of the 2.2.0 SDKs, about which we are feeling particularly excited: the “Video Driver”. Although the feature exists with parity in both platforms, today we’ll focus on the iOS-variant of the new API.
Here at TokBox we are always trying to expand and improve our range of features, tailoring these features in line with real world developer needs. That’s why we are excited to announce some pricing and storage updates.
We’re still receiving a lot of feedback on our beta so we’d like to extend a big ‘thank you’ to our community for this.
We have recently published an updated post about the Cordova plugin which you can read here. We’re looking forward to your contributions to this OpenTok Labs project and seeing what you create with Cordova.
Over the past weeks I have been working on an open sourced, community driven, Cordova Plugin for OpenTok SDK that will give you the ability to add webrtc live audio/video chat to your Android and iOS applications. In this blog post I hope to let the OpenTok community know that this project is available and if you are a web developer with limited Android or iOS experience, you can now build OpenTok mobile apps with ease using the technology you are familiar with.
Jump right into your own project! Since this project is open source, please file issues/concerns on the GitHub issue tracker and feel free to send pull requests!
A major vulnerability was uncovered yesterday which affects a majority of web service providers. The exploit is related to OpenSSL’s heartbeat extension which could enable a malicious attacker to access private keys. The bug has been present in OpenSSL since December 2011, and was brought to light yesterday. You can find more information about the exploit termed “Heartbleed” (CVE-2014-0160) here.
Our operations team reacted immediately to this and has taken the necessary steps to secure our infrastructure, ensuring the appropriate secure versions of OpenSSL are in place.