Handling connection events in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a connection event in Express?

A connection event in Express is an event triggered when a client connects to the server, allowing the server to respond or log the connection.

intermediate

How do you listen for connection events in an Express app?

You listen for connection events by attaching event listeners to the server object returned by app.listen(), for example using server.on('connection', callback).

beginner

What object do you use to handle connection events in Express?

You use the HTTP server object returned by app.listen() to handle connection events, not the Express app object itself.

intermediate

Why might you want to handle connection events in an Express app?

Handling connection events helps monitor active connections, log client activity, or manage resources like sockets for better server control.

beginner

Show a simple example of handling a connection event in Express.

const express = require('express');
const app = express();
const server = app.listen(3000);
server.on('connection', (socket) => {
  console.log('New client connected');
});

Which object do you attach a 'connection' event listener to in Express?

A The Express app object

B The response object

C The request object

D The server object returned by app.listen()

The 'connection' event is emitted by the server object returned by app.listen(), not by the Express app or request/response objects.

What does the 'connection' event provide as an argument to its callback?

A A socket object representing the client connection

B The HTTP request object

C The Express app instance

D The server configuration

The 'connection' event callback receives a socket object that represents the client connection.

Why is handling connection events useful in an Express server?

A To monitor and manage client connections

B To handle HTTP request routing

C To serve static files

D To parse JSON bodies

Handling connection events helps monitor and manage client connections, which is different from routing or parsing requests.

Which method starts the Express server and returns the server object?

A app.start()

B app.listen()

C express.createServer()

D server.connect()

app.listen() starts the server and returns the server object used to listen for connection events.

Can you listen for 'connection' events directly on the Express app object?

A Only if you use middleware

B Yes, the app object emits connection events

C No, you must listen on the server object

D Only in Express version 5+

The Express app object does not emit 'connection' events; you must listen on the server object returned by app.listen().

Explain how to handle connection events in an Express server and why it might be useful.

Think about the server object and what happens when a client connects.

Describe the difference between the Express app object and the server object regarding connection events.

Consider which object deals with network connections.

Practice

1. What does io.on('connection', callback) do in an Express app using Socket.IO?

easy

A. Runs the callback when a user disconnects

B. Runs the callback when the server starts

C. Runs the callback when a new user connects to the server

D. Runs the callback when the server shuts down

Solution

1. Step 1: Understand the event name 'connection'

   The 'connection' event triggers when a new client connects to the server.

2. Step 2: Understand the role of the callback

   The callback runs code to handle the new connection, such as setting up listeners.

3. Final Answer:

   Runs the callback when a new user connects to the server -> Option C

4. Quick Check:

   io.on('connection') = new user connected [OK]

Hint: Remember 'connection' means user joined [OK]

Common Mistakes:

• Confusing 'connection' with 'disconnect'
• Thinking it runs on server start
• Assuming it runs on server shutdown

2. Which of the following is the correct syntax to listen for a user disconnect event on a socket?

easy

A. io.on('disconnect', () => { /* code */ })

B. socket.on('disconnect', () => { /* code */ })

C. socket.emit('disconnect', () => { /* code */ })

D. io.emit('disconnect', () => { /* code */ })

Solution

1. Step 1: Identify the object to listen on

   The disconnect event is listened on the individual socket, not the io server object.

2. Step 2: Use the correct method and event name

   Use socket.on('disconnect', callback) to run code when that socket disconnects.

3. Final Answer:

   socket.on('disconnect', () => { /* code */ }) -> Option B

4. Quick Check:

   socket.on('disconnect') = user left [OK]

Hint: Listen on socket, not io, for disconnect [OK]

Common Mistakes:

• Using io.on instead of socket.on for disconnect
• Using emit instead of on to listen
• Listening disconnect on wrong object

3. What will be logged when this code runs and a user connects then disconnects?

io.on('connection', (socket) => {
  console.log('User connected');
  socket.on('disconnect', () => {
    console.log('User disconnected');
  });
});

medium

A. User connectedUser disconnected

B. User disconnectedUser connected

C. User connected

D. User disconnected

Solution

1. Step 1: When user connects

   The 'connection' event triggers, logging 'User connected'.

2. Step 2: When user disconnects

   The socket's 'disconnect' event triggers, logging 'User disconnected'.

3. Final Answer:

   User connected
   User disconnected -> Option A

4. Quick Check:

   Connect then disconnect logs both messages [OK]

Hint: Connect logs first, disconnect logs second [OK]

Common Mistakes:

• Assuming disconnect logs before connect
• Missing that disconnect logs separately
• Thinking only one message logs

4. Identify the error in this code snippet that tries to log when a user disconnects:

io.on('connection', (socket) => {
  socket.on('disconnect', () => {
    console.log('User disconnected');
  });
});

socket.on('disconnect', () => {
  console.log('Another disconnect');
});

medium

A. The second socket.on('disconnect') is outside the connection handler and socket is undefined

B. The first socket.on('disconnect') should be io.on('disconnect')

C. The disconnect event should be 'disconnected' not 'disconnect'

D. The console.log statements are missing semicolons

Solution

1. Step 1: Check where socket is defined

   Socket is only defined inside the connection callback, so outside it socket is undefined.

2. Step 2: Identify the error

   The second socket.on('disconnect') is outside the connection handler, causing a runtime error.

3. Final Answer:

   The second socket.on('disconnect') is outside the connection handler and socket is undefined -> Option A

4. Quick Check:

   socket undefined outside connection callback causes error [OK]

Hint: Use socket only inside connection callback [OK]

Common Mistakes:

• Trying to use socket outside connection event
• Confusing event names 'disconnect' vs 'disconnected'
• Ignoring scope errors

5. You want to broadcast a message to all connected users except the one who just connected. Which code inside io.on('connection', (socket) => { ... }) correctly does this when a user connects?

hard

A. socket.on('message', 'A new user joined')

B. io.emit('message', 'A new user joined')

C. socket.emit('message', 'A new user joined')

D. socket.broadcast.emit('message', 'A new user joined')

Solution

1. Step 1: Understand broadcast

   socket.broadcast.emit sends to all except the current socket.

2. Step 2: Compare options

   io.emit sends to all including current socket; socket.emit sends only to current socket; socket.on listens, not sends.

3. Final Answer:

   socket.broadcast.emit('message', 'A new user joined') -> Option D

4. Quick Check:

   Broadcast excludes sender, perfect for this case [OK]

Hint: Use socket.broadcast.emit to exclude sender [OK]

Common Mistakes:

• Using io.emit which sends to sender too
• Using socket.emit which sends only to sender
• Confusing emit with on