Over the course of this chapter, we covered each step of the signaling process. We walked through setting up a Node.js application, identifying users, and sending the entirety of offer/answer mechanisms between users. We also detailed disconnecting, leaving connections, and sending candidates between users.

You should now have a firm understanding of how a signaling server works. The server that we built is built to be simple and straightforward from a pure learning standpoint. We could fill an entire book up with new features that we could add to our server, such as authentications, buddy lists, and more. If you are feeling adventurous, feel free to add as many functionalities as you would like to our implementation.

We also covered a little about real-world signaling applications. This is just the tip of the iceberg as far as information about signaling is concerned. There are a wealth of use cases and implementations out there for WebRTC signaling. My recommendation would be to collect your requirements early and stick to the simplest solution that meets all of your requirements. This could be anything from a simple WebSocket server to the most complex SIP implementation.

In the next chapter, we will be integrating our server with an actual WebRTC client. This will enable us to make WebRTC connections between users at different locations. This is the beginning of a full-fledged WebRTC application that can be used to connect people all over the world.