6 ms·
Multi-User Video Conference with WebRTC
- boothead 12y agoThis looks pretty nice. I might use this as my next example app I port over to GHCJS for a comparison :-)
- benaston 12y agoDestroyed by the traffic. Can someone post a link to the github repo if one exists?
- boothead 12y agoHere you go: https://github.com/mgechev/angular-webrtc https://github.com/mgechev/angular-webrtc
- malux85 12y agohttps://mgechev-webrtc.herokuapp.com/#/room/471 https://mgechev-webrtc.herokuapp.com/#/room/471
- fcanela 12y agoI will stay a little in this room to test if this works. BTW if you see me say "hi", I'm friendly :)
- dubcanada 12y agoNot anything against this. But I don't see the part that is ~300 lines of Javascript. All I see is two minified files (which look to add up to around 300kb's of JS). And a 80 loc file. Which one should I be looking at?
- own3r 12y agoTake a look at the source code at GitHub, this is only the demo https://github.com/mgechev/angular-webrtc https://github.com/mgechev/angular-webrtc
- higherpurpose 12y agoI assume this uses the old WebRTC API, not the newer, more Javascript-focused ORTC?
- 0x006A 12y agoSo far no browser supports ORTC, how could it?
- tlrobinson 12y agoLooks like there's a shim: https://github.com/openpeer/ortc-js-shim https://github.com/openpeer/ortc-js-shim
- 0x006A 12y agothat's a link to an empty repository. there might be a shim at some point but so far not.
- tlrobinson 12y agoWhoops, should have looked more closely.
- matthijs_ 12y agoThe original blog post: http://blog.mgechev.com/2014/12/26/multi-user-video-conference-webrtc-angularjs-yeoman/ http://blog.mgechev.com/2014/12/26/multi-user-video-conferen...
- zo1 12y agoWhat is the benefit (if any) of using WebRTC over plain old web sockets? I ask because I'm currently working on a project that uses web sockets, and it's been really easy to use. Now, if there is valid reason for me to switch over, I'm all ears?
- onion2k 12y agoWebRTC is peer-to-peer - two people can transfer data between their browsers without anything hitting a 3rd party server. (You still need a server to broker connections, but that's all.) WebRTC isn't supported on IE or Safari though, so it's kind of redundant for anything but experiments at the moment.
- mgechev 12y agoWebRTC establishes p2p connection over which you can transfer media streams or other data via the data channels provided by the API. Using WebSockets you cannot make two browsers communicate directly without using any proxy in the middle. So WebRTC has the following benefits: - establish p2p connection between two browsers (not necessary required to be browsers) - transfer media (audio/video) efficiently - allows data streaming over UDP/TCP/SCTP (you can use one, depending on your application type - for example UDP if you're looking for performance over reliability) And the following drawbacks: - requires more complex architecture (for the NAT traversal procedures via ICE) - you have no guarantee that the connection between the peers will be established (in case of symmetric NATs in front of the peers you want to connect) - has more complex API
- johansch 12y agoRegarding NAT: does it do anything to attempt to solve this problem, or is that entirely left to the app developer?
- mgechev 12y agoYou can use TURN server in case of symmetric NATs. RTCPeerConnection can accept a list of TURN servers and fallback to them in case p2p connection cannot be established.
- Fastidious 12y agoFor those of us who might not know, this is using Node.js, correct?
- myhnuserr 12y agoYeah, JavaScript on both - front-end and back-end.
- Fastidious 12y agoThanks!
- CSDude 12y agoIt might be a better idea to give longer and non-predictable room ids