CODEWITHSUNDEEP
node.jswebrtckurentoeasyrtcsimplewebrtc
h_h10a
h_h10a

Reputation: 459

SimpleWebRTC, EasyRTC and Kurento .. what's the difference?

Hello I am new learning WebRTC and i am a bit confused, i understood that WebRTC works peer to peer but we need signaling, which of SimpleWebRTC, EasyRTC and Kurento can help doing that and why do we need them if node.js can do it? if they are not for signaling then what are they for exactly? frontend? backend? and what's the difference between them? Thanks!

Upvotes: 3

Views: 3563

Answers (2)

Buddhika Jayawardhana
Buddhika Jayawardhana

Reputation: 131

Kurento: Even though webRTC is peer-to-peer sometimes you need more control over media. In kurento all the traffic go through Kurento Media Server(Where you can do things such as record media or add effects). To use Kurento you have to install Kurento Media Server and in frontend you have to use Kurento's java-script library

SimpleWebRTC : This is not used for signaling. It's a front-end java-script library for webRTC. To do signaling for simpleWebRTC you have to build a separate signaling server(or you can use an existing one like signalmaster).

Upvotes: 7

fycth
fycth

Reputation: 3489

They all are for signaling (mostly). And also for those people who don't want to get deep into all this WebRTC stuff, which is still under active development.

So, if you don't want to get into WebRTC but would like to focus on more important features of your project, then one of those frameworks/libraries is your solution.

If you think you're good at WebRTC, then you don't need 3rd-party frameworks.

From my personal perspective:

  • using of 3rd-party frameworks is not a good choice, because the 3rd-paty signaling server it is plus one point of possible issues with your project, - since you depend on the 3rd-party server (its API, latency, network problems, etc.)
  • all the mentioned frameworks/libraries are not much flexible. Since WebRTC is under active development and there is still no standard (RFC) for it, many WebRTC features can be implemented as a 'dirty hack' only (like high quality stereo audio broadcasting) - and there is often no solution for achieving that by using the mentioned frameworks.

So, if you need a simple WebRTC video-chat - using of the mentioned libraries might be a good solution. From the other hand, if you're going to utilize WebRTC heavily in your project - probably, the best choice is to rely on your own codebase only.

Upvotes: 2

Related Questions