{"id":63,"date":"2014-06-02T16:43:40","date_gmt":"2014-06-02T14:43:40","guid":{"rendered":"http:\/\/www.meetecho.com\/blog\/?p=63"},"modified":"2016-12-22T18:17:12","modified_gmt":"2016-12-22T17:17:12","slug":"habemus-data-channels","status":"publish","type":"post","link":"https:\/\/www.meetecho.com\/blog\/habemus-data-channels\/","title":{"rendered":"Habemus Data Channels!"},"content":{"rendered":"

Work is moving on fast on our WebRTC gateway Janus<\/a>. Just these latest weeks, besides improving the overall architecture and performances, we added several features that we were interested in supporting, like RTCP muxing, bundling, Trickle ICE and more.<\/p>\n

One of the most interesting new features provided by WebRTC, though, are Data Channels<\/a>, a way to allow WebRTC users to exchange real-time data other than audio and video in a peer-to-peer fashion. So far, Janus didn’t support them yet. And I mean so far because, as you might have guessed by the enthusiastic and self-revealing post title, we finally implemented support for Data Channels as well!\u00a0This was made possible thanks to the help of the excellent usrsctp<\/a> library, which allows for user space usage of SCTP, and was already used for Data Channels by both Chrome and Firefox.<\/p>\n

Data Channels in Janus are a really exciting opportunity. The image below shows a first example of the new Data Channel integration within the Echo Test plugin demo:<\/p>\n

\"Data<\/a>
Data Channels in the Janus EchoTest demo<\/figcaption><\/figure>\n

The EchoTest plugin does a very simple manipulation: whenever it receives a string through a Data Channel, it builds a new one that integrates it, and returns it to the user as it does for audio and video frames. Of course this is a very trivial and silly usage of Data Channels, but it indeed proves that data is available and that it can be messed with. Integrating this in other plugins (e.g., to provide real-time chat features to a video call or conference) or writing new plugins from scratch that take explicit advantage of this functionality would be just as easy. If you consider that you can reflect the same Data Channel message to several different users at the same time, you can understand why we’re so excited!<\/p>\n

That said, at the time of writing this new feature has not been pushed to GitHub<\/a> yet. We’ve just finished integrating SCTP and DataChannels within the Janus core and, since it took some changes here and there, we want to make sure nothing else broke in the process! This won’t take more than a few days, though, so if you’re as excited as we are about it, stay tuned and get ready to play with it!<\/p>\n","protected":false},"excerpt":{"rendered":"

Work is moving on fast on our WebRTC gateway Janus. Just these latest weeks, besides improving the overall architecture and performances, we added several features that we were interested in supporting, like RTCP muxing, bundling, Trickle ICE and more. One of the most interesting new features provided by WebRTC, though, are Data Channels, a way to allow WebRTC users to exchange real-time data other than audio and video in a peer-to-peer fashion. So far, Janus didn’t support them yet. And I mean so far because, as you might have guessed by the enthusiastic and self-revealing post title, we finally implemented support for Data Channels as well!\u00a0This was made possible thanks to the help of the excellent usrsctp library, which allows for user space usage of SCTP, and was already used for Data Channels by both Chrome and Firefox. Data Channels in Janus are a really exciting opportunity. The image below shows a first example of the new Data Channel integration within the Echo Test plugin demo: The EchoTest plugin does a very simple manipulation: whenever it receives a string through a Data Channel, it builds a new one that integrates it, and returns it to the user as it does for audio and video frames. Of course this is a very trivial and silly usage of Data Channels, but it indeed proves that data is available and that it can be messed with. Integrating this in other plugins (e.g., to provide real-time chat features to a video call or conference) or writing new plugins from scratch that take explicit advantage of this functionality would be just as easy. If you consider that you can reflect the same Data Channel message to several different users at the same time, you can understand why we’re so excited! That said, at the time of writing this new feature has not been pushed to GitHub yet. We’ve just finished integrating SCTP and DataChannels within the Janus core and, since it took some changes here and there, we want to make sure nothing else broke in the process! This won’t take more than a few days, though, so if you’re as excited as we are about it, stay tuned and get ready to play with it!<\/p>\n","protected":false},"author":1,"featured_media":64,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,4],"tags":[],"class_list":["post-63","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-janus","category-webrtc"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t