3 ms·
If you do your homework you quickly find out that a signaling server is required (it’s written into the WebRTC spec itself) and that STUN/TURN is needed for NAT
by corytheboyd 6y ago
If you do your homework you quickly find out that a signaling server is required (it’s written into the WebRTC spec itself) and that STUN/TURN is needed for NAT traversal. You should use your common sense and not want to lean on public shared offerings of either of those IMO, and the PeerJS docs do call this out
- maxmcd 6y agoPeerJS is also using a short ID as a reference and needs more server support than just a STUN server.
- corytheboyd 6y agoRight, it’s called a signaling server, which is mainly what PeerJS seems to be. You need a method of connecting peers through the signaling server, they decided on generating uuids that are shared out of band or through a peer discovery api. You can do this pretty much however you want, the spec doesn’t clarify at all by design.
- dboreham 6y agoDidn't the parent say exactly that?
- corytheboyd 6y agoPretty much, I guess I’m not adding much more than backup claims here, which I don’t personally see issue with.