How do you handle newcomers efficiently in WebRTC signaling? -

Signaling is not addressed by webRTC (even if we have a starting point), but what I understand It works like this:

1. The client tells the server that it is available on X
2. the server has kept the information and maps it for an identifier
3. The other customer comes and sends
4. The other client will make it a connection information. Uses and sends it to the server
5. The server sends it to the client first
6. Both clients can now talk

   Everything is good and good, but if a third customer comes then what can happen to yourself?

   You have to do all the things again, which believe that the first two clients are still connected to the server, waiting to signal a signal, and start the exchange process again. So that they can get 3 client connection information.

   For every client the server requires a permanent link (long voting, webscock, etc.)? If so, is there a way to do this efficiently?

   Because I do not see the point of being a webtc if I have to set up nodes or tornadoes and it is increased to my number of users, it does not piss me much.

   Please tell me I have remembered something.

   What about chat systems? Do you really need to have permanent links on the server for each client? Of course, because otherwise you have no way to keep track of the user's situation. This "permanent" link can be done differently: You have mentioned web site and long voting, but ordinary periodic XHR voting also works (although it will affect UX on the basis of intervals).

   So it's like a chat system, except that the media stream is P2P for less delay. Once a P2P WebRTC connection is established, the server may die and, of course, P2P The connection will be kept between two customers. What do I mean: Both users can always block your server, once the P2P connection is established and still connected together in the wild Internet.

   Understand me well: Once the P2P connection is established, your server requires any more WebRTC signaling. The connection is only necessary to keep track of the situations.

   So it depends on your application. If you want to keep the status of users and make them visible to others, then you are in the same situation as the chat system: to make sure that their situations are synchronizing, one surefire Keep the link. Otherwise, your server is present to connect together and it is not needed later on. An example of the latter situation is: A user goes to a webpage, the webpage provides a new room URL, the user will be redirecting this URL to Sharing another colleague with another means, the other colleague joins the room, the server joins them together, WebRTC signaling) and then forgets them. They are now connected until one of them breaks the link. Just like

   Rather than having a connection to a client, rather than a central server, a network network can also be considered, although implementation is difficult.