Connection passed with Message Event about websocket-node HOT 1 CLOSED

I don't conceptually agree with this suggestion. It would indeed make one particular coding style simpler, but the culture with JavaScript and Node is to use closures to maintain a reference to the connection at hand. Also, the close event on the connection object does not (any longer) pass the connection as a parameter. It used to, errantly, but the official documentation never showed the connection being passed. The examples did, unfortunately, show it used that way, unnecessarily, and has been revised to remove the connection parameter.

Example of correct idiomatic usage:

ws.on('connect', function(connection) {
    // the connection parameter is available within the closure, so any further
    // functions defined inside this function will have access to it.
    connection.on('message', function(message) {
        // connection is still available here:
        if (message.type !== 'utf8') { return; }
        console.log("Message from " + connection.remoteAddress + ": " + message.utf8Data;
    });
    connection.on('close', function() {
        console.log("Connection from " + connection.remoteAddress + " has been closed");
    });
});

Where this breaks down is if you use a single event handler function, defined once and used for every connection, passed by reference to the on() method. Don't do that.

from websocket-node.