Twilio WebRTC vs DIY WebRTC -
is webrtc going free web developers set video calls on web pages? why twilio having pricing 25c per mins video calls, going expensive small guy mange video calls on web hosting servers?
any advice deep webrtc already?
some of comments above not informed.
wrote, since bandwidth needed in case of media relay higher well.
not entirely true, transmission happens between peers(browsers), servers used signalling(relaying ip addresses of connecting peers , more info), can route transmission central server(for fail overs), can surely without free.
webrtc free , can setup whole thing on own without having shell out penny. bit hard , mitigating fail-overs difficult, can free.
tokbox or twilio charge money because these tools abstract rigid complexities of setting up, running , managing fail-overs in webrtc application.
in tokbox's case:
you don't need setup stun, turn servers, don't have worry integration android or ios clients, provide plugin ie too, out of box , have concentrate on application logic rather webrtc nuances. big plus.
both relay , routed schemes came in box hence can write
fail-over scenarios if relay communication fails. although there javascript based frameworks in cleaner manner.- it adds slew of other goodies in building android , ios clients without pain.
stun or turn servers used signalling purpose, , signalling happens before actual transmission. signal small , carries ip address of both browsers(machines running browsers). transmission communication done between browsers(peer peer) themselves, no server involved.
your relay not happening central server don't have pay outgoing bandwidth cost.
to setup turn server,
use server, build , put rackspace/amazon web services instance , turn server. it, setup application , have fun webrtc free.
rfc5766-turn-server
if wish use more free framework ease more, check out: easyrtc , peerjs
enjoy developing webrtc....
Comments
Post a Comment