WebRTC Data Channels vs WebSockets

WebRTC Data channels vs. WebSocketsSignaling 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.

0 Comments Read More

Releasing the OpenTok Plugin for Internet Explorer 8-11

opentok plugin for internet explorerToday we’re pleased to announce support for Internet Explorer versions 8 & 9 through our OpenTok Plugin. (The previous version of the plugin supported Internet Explorer 10 & 11.) Now you can leverage the same native WebRTC features enjoyed by Chrome and Firefox users in Internet Explorer versions 8 through 11.

Our release today means that your OpenTok powered applications will automatically start working with Internet Explorer 8 and 9. As always, we’re focused on bringing the best possible real time communications experiences to the endpoints you know and use. This is just one more step forward in our journey towards making the OpenTok platform endpoint agnostic.

0 Comments Read More

Buy vs. Build

BVBWhen 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.

1 Comment Read More

Announcing the end-of-life of the OpenTok 1.0 platform

LogoOpenTokCome 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.

0 Comments Read More

WebRTC for Enterprise: Challenges and Solutions

enterprise

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.

Signaling:

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.

0 Comments Read More