SocketIO and a large number of events?

Question

Node.js

The question arose, in the vast majority of socket examples, the following construction is used:

io = require('socket.io').listen(httpsServer);
io.on('connection', function(socket) {
  socket.on('listener1', function(e) {
    //code
  }),
 socket.on('listener2', function(e) {
    //code
  }),
  ...etc
});

The question is, is it correct to write code like this? After all, when connecting 100 people, the node will create N * 100 wiretapping events. How to get out of such a situation?

Answer 1

Yes, there is no "situation". When 100 clients connect, 100 socket objects will be created - each with a unique ID. And "listeners" of events are not asked, they only listen to them and, upon receipt, give them to handlers - this is an abstraction common to all connections.

Answer 2

In my opinion the example somehow looks strange.
"socket.on" occurs on some event, not on the arrival of a new user.
That is, for example, a client (one or a thousand) says A on the server side

io = require('socket.io').listen(httpsServer);
io.on('connection', function(socket) {
  socket.on('getUserInfo', function(e) {
    //code
     ...
    socket.emit('sendUserInfo', data)
  })
});

That is, it does not depend on the number of clients. Though yes, open TCP connections with each client will hang.