4 ms·
In my opinion their secure communication acts as a double-edge sword for WebRTC. Now one-to-many streaming is complicated since you cannot easily add a man-in-t
by samsonradu 10y ago
In my opinion their secure communication acts as a double-edge sword for WebRTC. Now one-to-many streaming is complicated since you cannot easily add a man-in-the-middle streaming server like you'd do in a normal setup. Trying to broadcast to >5 users on a Chrome tab really heats up my laptop.
- TD-Linux 10y agoIn fact, you can easily add a streaming server in the middle (and many-participant WebRTC servers do exactly this), it's just that you can't have it happen unintentionally.
- deleted 10y ago[deleted]
- samsonradu 10y agoCould you please elaborate? I've looked over the Kurento[1] Media Server page but I didn't find it that 'easy'. Would you use a tool alike or implement the negotiation yourself? [1] http://doc-kurento.readthedocs.io/en/stable/introducing_kurento.html#webrtc-media-servers http://doc-kurento.readthedocs.io/en/stable/introducing_kure...
- TD-Linux 10y agoPerhaps an easier example is Janus, such as their 2-way demo that forwards all media packets through the Janus server: https://janus.conf.meetecho.com/videocalltest.html https://janus.conf.meetecho.com/videocalltest.html Or the more complex demo, for a video conference where all media is forwarded through the Janus server: https://janus.conf.meetecho.com/videoroomtest.html https://janus.conf.meetecho.com/videoroomtest.html