WebRTC is already around for quite some time. Even though it’s hard to believe, first version of Chrome with WebRTC support (enabled by default) has been released almost 3 years ago. During all these years browser vendors have been trying to reach maximal compatibility with specification, and developers have been struggling with different implementations. We all were curious about big players’ reaction regarding new technology and when (or if) they are going to join the movement. But there were no doubts that sooner or later WebRTC will be supported everywhere.

So what do we have after 3 years of evolving? Well, the current situation is not so good as most of optimists expected. But at least, it’s more clear now what might happen in the future.

One of the base features of WebRTC is an ability to transfer data between peers secure and on high speed. Data exchange is realized via Data Channel (also called RTCDataChannel) API.

Data channel is basically a one direction stream which is used to share data in peer-to-peer connection. For example during video call data is sent via 2 channels: one for outgoing video stream and other for audio. Optionally we can create additional data channels (up to 65535 per connection), for instance to send file to other peers.

Every day in-browser video communication getting more and more popular among web apps and services. Video calling and messaging makes old-fashioned contact form or support chat look modern and renewed as it brings new experience for instant communication — the same way as we ask shop assistant to help us with selecting new TV we can ask support engineer to help us with making purchase and describe delivery policy of web shop. And what is even more thrilling, is that this communication is just few clicks away.