Socket.IO - Revision history

Todd at 13:31, 1 March 2026

2026-03-01T13:31:16Z

Todd at 13:31, 1 March 2026

2026-03-01T13:31:03Z

Show changes

Todd: /* Installing Socket.IO */

2024-06-06T20:38:16Z

Installing Socket.IO

Todd: /* Installing Socket.IO */

2024-03-21T23:56:04Z

Installing Socket.IO

Todd: /* The Chat Client */

2023-06-08T15:13:06Z

The Chat Client

Todd: /* Resources */

2022-10-31T16:53:00Z

Resources

Todd: /* The Chat Server */

2021-03-24T15:44:43Z

The Chat Server

Jasonren: /* The Chat Server */

2020-11-11T20:06:09Z

The Chat Server

Jasonren: /* The Chat Server */

2020-11-08T23:12:35Z

The Chat Server

Jasonren: /* The Chat Server */

2020-11-08T18:25:02Z

The Chat Server

← Older revision		Revision as of 13:31, 1 March 2026
Line 202:		Line 202:
	* Rooms documentation: https://socket.io/docs/v4/rooms/		* Rooms documentation: https://socket.io/docs/v4/rooms/

−	[[Category:Module 7]]	+	[[Category:Module 5]]

@@ Line 13: / Line 13: @@
 </source>
-'''Note:''' If you pass the ''-g'' to ''npm install'', then the package will be installed "globally" on your instance, so all Node.JS projects will be able to use it.  However, this is not recommended for all projects.  [https://web.archive.org/web/20120614221759/http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/ Read Node.JS's justification here.]
+'''Note:''' If you pass the ''-g'' to ''npm install'', then the package will be installed "globally" on your instance, so all Node.JS projects will be able to use it.
 == Messaging ==

@@ Line 13: / Line 13: @@
 </source>
-'''Note:''' If you pass the ''-g'' to ''npm install'', then the package will be installed "globally" on your instance, so all Node.JS projects will be able to use it.  However, this is not recommended for all projects.  [http://blog.nodejs.org/2011/04/06/npm-1-0-link/ Read Node.JS's justification here.]
+'''Note:''' If you pass the ''-g'' to ''npm install'', then the package will be installed "globally" on your instance, so all Node.JS projects will be able to use it.  However, this is not recommended for all projects.  [https://web.archive.org/web/20120614221759/http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/ Read Node.JS's justification here.]
 == Messaging ==

@@ Line 94: / Line 94: @@
     <head>
        <script src="/socket.io/socket.io.js"></script>
-       <script type ="text/javascript">
+       <script>
        var socketio = io.connect();

@@ Line 129: / Line 129: @@
 == Resources ==
-The [http://socket.io/ Socket.IO web site] has concise examples that tell you pretty much all you need to know in order to build a functional Socket.IO web application.
+The [http://socket.io/ Socket.IO web site] has concise examples that tell you pretty much all you need to know in order to build a functional Socket.IO web application. A helpful discussion on how to use rooms with Socket.IO can be found [https://socket.io/docs/v4/rooms/ here].
 [[Category:Module 7]]

@@ Line 63: / Line 63: @@
 // Import Socket.IO and pass our HTTP server object to it.
-const socketio = require("socket.io")(server, {
+const socketio = require("socket.io")(http, {
      wsEngine: 'ws'
 });

@@ Line 55: / Line 55: @@
          // This callback runs when the client.html file has been read from the filesystem.
-         if (err) return resp.writeHead(500);
+         if (err) return res.writeHead(500);
          res.writeHead(200);
          res.end(data);

@@ Line 43: / Line 43: @@
 <source lang="javascript">
 // Require the packages we will use:
-var http = require("http"),
+const http = require("http"),
-	socketio = require("socket.io"),
+    fs = require("fs");
-// Listen for HTTP connections.  This is essentially a miniature static file server that only serves our one file, client.html:
+const port = 3456;
-var app = http.createServer(function(req, resp){
+const file = "client.html";
-	// This callback runs when a new connection is made to our HTTP server.
+// Listen for HTTP connections.  This is essentially a miniature static file server that only serves our one file, client.html, on port 3456:
+const server = http.createServer(function (req, res) {
-	fs.readFile("client.html", function(err, data){
+    // This callback runs when a new connection is made to our HTTP server.
-		// This callback runs when the client.html file has been read from the filesystem.
+    fs.readFile(file, function (err, data) {
-		if(err) return resp.writeHead(500);
+        // This callback runs when the client.html file has been read from the filesystem.
-		resp.writeHead(200);
-		resp.end(data);
+        if (err) return resp.writeHead(500);
-	});
+        res.writeHead(200);
 });
-app.listen(3456);
+server.listen(port);
-// Do the Socket.IO magic:
+        console.log("message: " + data["message"]); // log it to the Node.JS output
-var io = socketio.listen(app);
+        io.sockets.emit("message_to_client", { message: data["message"] }) // broadcast the message to other users
-io.sockets.on("connection", function(socket){
+    });
 });