The number of P2P technologies addressing video delivery is growing, and they differ significantly in approach and implementation. It is important to be aware of these differences when looking at P2P for video delivery. Being a provider, we know what they are and thought it may be helpful to map them out. As a point of reference, we will also explain where Viblast stands in each category.

It is not enough to have a powerful technology, it needs to be user-centered as well: both easy to understand and easy to use and track results. That is why today we are thrilled to announce the Viblast Cloud Service Customer Portal!

Today I’ll offer a very brief Friday read covering some special cases of WebRTC data channel (DC) behavior - short and sweet as they say.

Let’s return today to the example of a file-sharing like app used in the previous post, WebRTC data channel: Optimum message size. Imagine that the app splits a big file into smaller chunks of 16 Kbytes and then simply sends all chunks at once. What would happen?

This article is the fifth in a series on the topic of the WebRTC data channel. All posts are based on a talk our Chief Architect, Svetlin Mladenov, delivered during the WebRTC conference expo Paris 2014. The accompanying slides are available here and the entire lecture itself can be seen on our YouTube channel.

Streaming Media’s Dan Rayburn published an insightful commentary this week about the somewhat controversial streaming optimization product vertical. He summarized solutions in this vertical thus: “While many of them have very different solutions, the goal of all of them is the same. To reduce the size of video bitrates, without reducing quality.”

Let’s pick things up where we last left off - after we went over the key WebRTC data channel (DC) characteristics in the previous post, today we’re going to explore one specific topic: signaling and establishing a connection.

After exploring how the SCTP implementation changed WebRTC forever and for the better, in this post, we will go over the main characteristics of WebRTC data channel's latest implementations.

[Viblast in the media - originally published at bloggeek.me on 15 Jan 2015]

One of the areas where WebRTC’s data channel makes a lot of sense is in distributed content delivery, where peers consuming the content cooperate with each other to receive it. One of the vendors in this space is Viblast, a company I met almost a year ago. I recently reached out to Lubomir Chorbadjiev, co-founder and CTO, and asked him a few questions about Viblast and their use of WebRTC. Here’s what he had to say.

Streaming high quality video requires that a demanding list of conditions be met. First, you need reliable infrastructure. The goal is to guarantee delivery and a specific quality of service (QoS). Some large companies simply invest in extra capacity or contract alternative providers as a form of protection against outages or buffering. That said, ABC’s Oscars 2014 live stream showed how things could go wrong even when you’re a major TV network.