3 ms·
The protocol and spec mostly, but also the establishment dance and too many knobs. Which client and server libs are you using? Chances are if you dig in their d
by klabb3 4y ago
The protocol and spec mostly, but also the establishment dance and too many knobs. Which client and server libs are you using? Chances are if you dig in their deps it’s messy.
It’s also designed for real-time video and audio (udp), so reliable high-bandwidth streaming p2p apps takes a back seat.
That doesn’t mean it’s not the right choice to build stuff with today, especially browser based real-time apps! I’m all for webrtc getting easier.
- forgotusername6 4y agoI didn't use anything other than the basic webrtc examples from github and a rather basic exchange using a web socket (server was express). Obviously not completely P2P because you need to exchange capabilities somehow. Tbh it probably took me longer to get the domain and coturn set up than the webrtc. I didn't look into how much bandwidth was being used. I was mainly using it for 1-4 person calls during lockdown. I wanted to write a video calling app that I could have full control of.
- palata 4y agoIt's always easy to run a variant of the main example of a library. The question is: how difficult does it get when you want to do something slightly different?