Chapter 6Managing Multipeer Connections
If you’re like me and have a habit of opening way too many browser windows and tabs while you’re working, you might have encountered mysterious problems and errors at some point during your peer-to-peer WebRTC work. Perhaps you thought your app had stopped working, only to discover two browser windows connected on your app’s namespace already—before you accidentally connected a third.
But even if you’ve been more careful than that, let’s prove the connection limits on a peer-to-peer app. Fire up the starter app for this chapter—which contains peer-to-peer logic and the audio features you built in the last chapter—by running npm run start and pointing to the same namespace off of https://localhost:3000/multipeer/ ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access