This is a Livecoding Recap – an almost-weekly post about interesting things discovered while livecoding. Usually shorter than 500 words. Often with pictures. Livecoding happens almost every Sunday at 2pm PDT on multiple channels. You should subscribe to ￼My Youtube￼ channel to catch me live.
It didn’t work. We don’t have a mesh network yet. But we’re so close that I can almost smell it.
This slide from my WeAreDevelopers talk 👇
Previously we’ve figured out how to connect two browsers running on different computers with a video connection. Signaling server helps with the initial handshake, then browsers communicate directly using WebRTC. No more server.
WebRTC also supports so called data channels using RTCDataChannel.
It works like this:
- Use signaling server to establish a peer connection
- Add a data channel to said connection
- Send from each side
Data can be anything. We’re using
"Hello World" strings for now, serialized JSON objects later. Rumors say you could send whole files.
This all sounds very simple. Even when you look at the code that’s required.
We add a
RTCDataChannel to our peer connection and attach a bunch of event handlers. Errors for complaining, messages for printing, and we try to send a message when the channel opens.
The cool part is that we can attach this channel before a connection is fully established.
See, both clients finish with saying
Data channel open.
But no data is sent or received, and there’s no error. 🧐
I suspect this is because while the data channel is open, the peer connection itself is not established. That pesky WebRTC lifecycle error about doing some thing or another in the wrong step.
This part used to work. Therefore, I must have broken something when deleting a bunch of code that seemed unnecessary.
We also generally spent a lot of time mucking around making this lifecycle more robust because it was hella flaky before.
PS: You should also follow me on twitter 👉 here.
It's where I go to shoot the shit about programming.