如何在Express+Socket.IO中识别并停止指定定时Socket事件

Got it, let's break down how to fix this. The core issue with your current code is that you're not tracking each interval ID tied to its respective socket event name. Plus, your /stop route isn't correctly receiving the target socket name. Here's a step-by-step fix:

Key Changes Needed #

• Track Intervals: Store each interval ID in an app-level object mapped to its event name (so we can find and stop it later).
• Fix Loop Scope: Use let instead of var in your loop to capture the correct event name for each interval.
• Receive Socket Name: Get the target event name from a query parameter in the /stop route (since req.socketname isn't a standard property).
• Clean Up Duplicates: Clear existing intervals when starting new ones to avoid overlapping instances.

Modified Code #

1. Initialize Interval Tracker (in your main app file) #

First, add an object to your Express app's locals to track intervals across routes:

// In app.js or wherever you initialize your Express app
app.locals.socketIntervals = {};

2. Updated /start Route #

router.get('/start', function(req, res, next) {
  const io = req.app.get('socketio');
  const socketlist = [{name:"firstsocket"},{name:"secondsocket"}];
  const intervalTracker = req.app.locals.socketIntervals;

  // Clear any existing intervals to prevent duplicate runs
  Object.values(intervalTracker).forEach(intervalId => clearInterval(intervalId));
  req.app.locals.socketIntervals = {};

  for (let key in socketlist) { // Use let for block-scoped variable
    const socketName = socketlist[key].name;
    // Store the interval ID mapped to its event name
    intervalTracker[socketName] = setInterval(() => {
      const JsonObj = { marks: `${socketName} ${parseInt(Math.random()*100)}` };
      io.emit(socketName, JsonObj);
    }, 2000);
  }

  res.send('Both socket events started successfully');
});

3. Updated /stop Route #

router.get('/stop', function(req, res) {
  const targetSocket = req.query.socketname; // Get event name from query param
  const intervalTracker = req.app.locals.socketIntervals;

  if (targetSocket && intervalTracker[targetSocket]) {
    // Stop the interval and remove it from the tracker
    clearInterval(intervalTracker[targetSocket]);
    delete intervalTracker[targetSocket];
    console.log(`Stopped socket event: ${targetSocket}`);
  } else {
    console.log(`No active socket event found for: ${targetSocket}`);
  }

  res.redirect('/');
});

How to Use #

• To start both events: Visit /start (or trigger it via your client button).
• To stop a specific event: Call /stop?socketname=firstsocket or /stop?socketname=secondsocket from your client button click.

Explanation #

• app.locals.socketIntervals: This persists across all routes and requests, so we can access the interval IDs anywhere in our app.
• let in Loop: Unlike var, let creates a block-scoped variable for each loop iteration, ensuring each interval uses the correct socketName.
• Query Parameter: Using req.query.socketname lets you pass the target event name from the client (e.g., via a button click that makes a GET request to /stop?socketname=firstsocket).

内容的提问来源于stack exchange，提问作者usersam