WebRTC and Phoenix, when μ Seconds aren't Fast Enough

on YouTube ↗37m

" summary

WebRTC plus Phoenix actually ships a working peer‑to‑peer voice app called Team Chat using Phoenix.presence for signaling and SimplePeer for the browser side; about 80 lines of JavaScript and a five‑line offer/answer flow make calls connect. Connections hit limits (browsers handle ~six video peers), trickle ICE and TURN servers decide whether peers connect or proxy, Safari lacks full support, and the demo and open‑source code do work. Phoenix.presence signaling trickle ICE speeds things up

AI-written summary · about

" chapters (33)

1. 0:00Introduction
2. 1:05TeamChat
3. 1:42Overview
4. 1:57What is WebRTC
5. 2:29Google Hangouts
6. 3:11PeertoPeer
7. 4:22Discovery
8. 5:29Connection
9. 6:25Topology
10. 9:15WebRTC
11. 12:20Offer
12. 13:08Phoenix
13. 13:32Signaling
14. 14:52Realtime communications
15. 15:13SimplePeer
16. 15:51Demo
17. 19:45Code
18. 20:27Ice Protocol
19. 22:17Turn Server
20. 23:17Standardized Servers
21. 24:00Low Level Aspects
22. 25:19TCP vs UDP
23. 28:26The future
24. 28:44Web Audio
25. 29:23Voice Chat
26. 29:44Stream Rebroadcasting
27. 29:57Network Example
28. 31:05Canvas Support
29. 31:41Jen WebRTC
30. 32:11Phoenix Channels
31. 32:44Learn more about WebRTC
32. 33:38Dont rewrite your application
33. 34:09QA

" related talks

• 33mWebRTC Change Communications ForeverGreg Baugues · RailsConf 2014
• 33mWebRTC Change Communcations ForeverGreg Baugues · RailsConf 2014
• 32mElixir, Phoenix, and WebRTC - An Enterprise Class Soft Phone in the BrowserSteve Pallen · ElixirDaze 2016
• 24mMaking WebRTC awesomeHenrik Joreteg · CascadiaJS 2013
• 27mWebRTC: Real-Time CommunicationsYlia Kasianenko · OdessaJS 2015
• 38mReal-time Communication on MobileThomas Gorissen · Meta Refresh 2015
• 34mReal-time Communication – for Everyone!Lisa Larson-Kelly · beyond tellerrand Berlin 2014
• 34mReal-Time Communication for EveryoneLisa Larson-Kelley · GoRuCo 2014