5 ms·
The signaling server is where a lot of the real complexity comes from [1]. I even had to write my own from scratch for our production implementation. [1] https
by Hydraulix989 9y ago
The signaling server is where a lot of the real complexity comes from [1]. I even had to write my own from scratch for our production implementation.
[1] https://www.sococo.com/blog/webrtc-signaling-here-be-dragons https://www.sococo.com/blog/webrtc-signaling-here-be-dragons
- deleted 9y ago[deleted]
- joantune 9y agoDid you look into any of these: https://www.html5rocks.com/en/tutorials/webrtc/infrastructure/ https://www.html5rocks.com/en/tutorials/webrtc/infrastructur... before implementing that one?
- Hydraulix989 9y agoYes, that's the first Google result, and they suggested building your own using socket.io -- read my article, if you haven't already (but some of their other _stack_ suggestions are decent). Their ready-made signaling server suggestions are complete garbage (Signalmaster is buggy and incorrect).
- moron4hire 9y agoI've not found signalling to be complex at all. You're just forwarding messages from one user to another. The server in the middle doesn't need to know anything other than to whom the messages go. The one thing that is not handled in any material I've ever read on WebRTC: how to sequence more-than-two users joining a session at the same time, and how to recover from errors and stalled connection attempts (where the latter is a significant impediment to the former).
- Hydraulix989 9y agoLet me test your implementation then. ;-)
- GroSacASacs 9y agoHow did the situation evolve since 2014