Videos / Web Dev

Episode 15 of 16 · Web development, end to end

WebSockets and WebRTC: connections that stay open

Chapters

1. One question, one answer0:00
2. Asking again, and again0:16
3. Holding the request open0:32
4. The connection that stays0:49
5. And the other answer1:06
6. Hold the difference1:23
7. A letter asking to switch1:41
8. One oh one, and it is gone1:57
9. Frames, not requests2:13
10. Both ways at once2:31
11. Take the secure one2:47
12. What you gave away for it3:05
13. Every cord still plugged in3:22
14. Sticky by nature3:41
15. Two people, two processes3:58
16. The backplane4:15
17. The dead connection4:34
18. Reconnect politely4:50
19. Out of one microphone5:08
20. Media first5:23
21. Late is worse than lost5:40
22. There is no plaintext mode5:59
23. The data channel6:18
24. Peer to peer has a ceiling6:36
25. Two people, no addresses6:54
26. Offer and answer7:12
27. Nobody can reach you7:30
28. Gather and test7:48
29. The cheapest server here8:05
30. When the network refuses8:22
31. Two questions, three tools8:39
32. The one people forget8:55
33. Less machinery, one catch9:14
34. When both ends speak9:33
35. When it is media or milliseconds9:55
36. Side by side10:13
37. The whole thing10:32

WebSockets and WebRTC: connections that stay open. The web was built on one shape. You ask, the server answers, and it is over. Nothing the server learns afterwards can reach you. A price changed, a message arrived, a job finished,

Mark as watchedSaved in this browser only.