Skip to content

Latest commit

 

History

History
98 lines (58 loc) · 4.47 KB

easyrtc_faq.md

File metadata and controls

98 lines (58 loc) · 4.47 KB

EasyRTC: FAQ

What is WebRTC?

WebRTC allows real-time communications within the browser without the need for plugins. A few of its greatest benefits include:

  • Standardized methods of connecting to web cameras and microphones.
  • Peer to peer connections. Improves latency and reduces bottlenecks on the servers.
  • Standardized negotiation for steaming audio, video and data.

What is EasyRTC?

EasyRTC removes the pain associated with getting started with WebRTC with the following cool features:

  • Cross browser support.
  • Working source code.
  • Easy server install.
  • WebSocket server.
  • Single language for server and clients (Javascript).
  • Open Source and free!

Why is WebRTC Hard?

The WebRTC API is a mid-level API. That is to say, that while it insulates the developer from stuff like connecting to cameras or contacting TURN and STUN servers, it still requires the developers to implement an involved message passing scheme between clients to establish the peer to peer connection.

The EasyRTC framework provides that message passing scheme so that the developer can focus on the tasks that are actually relevant to them.

EasyRTC Requirements:

So far we have tested EasyRTC on Windows 7, 8, OS-X, Raspberry Pi, and Ubuntu 12.04 LTS where users have administrator or sudo access.

For the most part, if you can run Node.JS, you can run EasyRTC.

Is EasyRTC production ready?

Yes and no... The biggest barrier to EasyRTC being considered production ready is the current state of WebRTC, both in terms of the specification and browser support, is not complete. As for EasyRTC itself, it along with its sibling EasyRTC Enterprise have been in production use since May of 2013.

There is a lot of work still to go in providing additional features which production code will need. We invite all users to give us feedback as to what features you desire.

When will WebRTC be ready for production?

Currently the WebRTC W3C specification is still being finalized. The original posted date for reaching recommendation status was overly optimistic (Q1 2013). With implementation methods still being debated, be prepared for it to take until Q4 2013 (or longer).

As the specification gets closer to recommendation status, we expect those browsers which are currently working on WebRTC to better communicate with each other.

Some browsers may wait until after the standard reaches recommendation status to implement WebRTC.

How about Multi-way Conversations?

WebRTC doesn't support multicast or broadcast packets (currently), so the only way to do multi-way conversations is a star configuration: each peer establishes a connection to every other peer. The EasyRTC API will support this and we provide a demo.

Check out tawk.com for an in-production example.

Why use Node.js?

Node.JS is a powerful asynchronous server platform which has several qualities we find enduring:

  • Performs exceptionally well as a HTML5 socket server.
  • Easy to program for with a thriving open source community to back it up.
  • Multi-platform! Allows installs on Linux, Windows, and Macs.
  • The Node Package Manager provides an easy way to distribute and install EasyRTC.

Are there plans to integrating with SIP?

SIP is an extensive protocol, and developing a WebRTC platform which supports it in a way casual developers could use it would be difficult. Unless we can come up with a way to make this "easy", it won't happen. This does allow for SIP and VOIP gateways to implement WebRTC using EasyRTC.

Priologic Software has been working on SIP integration methods commercially (shameless plug).

How do I report bugs or ask for features?

We monitor both the Github issue tracker and the Google Groups discussion forum.

You Didn't Answer My Question!

Ask away on our forum. We do monitor it!