Lorenzo Miniero - 010: "Sounds like a plan!" Or how I added multistream to Janus using Unified скачать в хорошем качестве

Lorenzo Miniero - 010: "Sounds like a plan!" Or how I added multistream to Janus using Unified

Janus has so far been limited to 1-audio/1-video stream per PeerConnection: now that all browsers implement Unified Plan, support for multistream PeerConnections was added too. The talk will describe the related challenges, and how this opened the door to exciting enhancements and opportunities. One of the interesting features of WebRTC is the ability to multiplex multiple streams of the same type (audio, video and data) over the same channel, i.e., PeerConnection. That said, for a while consensus on the best way to signal this via SDP was divided among those who favoured the so called ""Plan B"", ""Unified Plan"", or even ""No Plan"". Even when consensus was reached on ""Unified Plan"", this division was still reflected in the related implementations: Chrome and Safari stuck with the ""Plan B"" they had already available, while Firefox implemented ""Unified Plan"" instead, thus making the respective multistream support non-interoperable. For this reason, to avoid implementing the same thing twice and in different flavours (and knowing one would have to be dumped sooner or later anyway), in Janus, our general purpose and open source WebRTC server implementation, we sticked to the 1-audio/1-video per PeerConnection limitation we had since day one. This never really limited the functionality we provided: in fact, multiple streams always were a possibility anyway, they just required multiple PeerConnections to work (e.g., in SFU scenarios). That said, there are several advantages in bundling multiple streams together, and so as soon as Chrome and Safari decided to implement ""Unified Plan"" as well, time was ripe to jump on the multistream train ourselves! Considering it might be interesting to developers that are about to tackle, or have already, a similar endeavour, this talk will describe the challenges we had to face in transforming a monostream core to multistream instead, especially in terms of internal structuring and the interactions with the plugins that add value to Janus itself, and the struggles this posed on the client side as well. The talk will also address some of the first integrations of this new multistream support in existing and widespread applications, and how this opened the door to exciting enhancements and opportunities for the future.