Socket连接下用户互见批量下载进度的问题解决求助

Hey there, the issue you're facing is a classic case of global variable overwrites and missing user-socket association logic. When a second user connects, your global socketUniqueID gets overwritten, and you're not properly targeting each user's own socket when sending progress updates. Let's fix this step by step:

What's Going Wrong Exactly? #

• socketUniqueID is a global variable—every new connection replaces the old value, meaning all progress updates end up going to the last connected user's socket.
• You tried using socket.id but didn't link it to the actual user ID (req.user.id), so there's no way to map which progress belongs to which user.
• The getApiAndEmit function relies on an undefined socketID and doesn't scope updates to the specific user's socket.

Fixed Code Implementation #

// Create a map to store each user's socket instance keyed by their user ID
const userSocketMap = new Map();

io.on("connection", (socket) => {
  // Grab the logged-in user's ID (ensure your auth middleware passes req.user to socket connections!)
  const userId = req.user.id;

  // Link the user to their socket in our map
  userSocketMap.set(userId, socket);

  // Set up the interval to send ONLY this user's progress to their socket
  const progressInterval = setInterval(() => {
    getApiAndEmit(userId, socket);
  }, 5000);

  socket.on("disconnect", () => {
    console.log(`User ${userId} disconnected`);
    // Clean up: remove the user from our map and clear the interval to avoid memory leaks
    userSocketMap.delete(userId);
    clearInterval(progressInterval);
  });
});

const getApiAndEmit = (userId, socket) => {
  try {
    // Emit progress to this specific socket using a consistent event name
    socket.emit("batch-download-progress", { batchdata: fetchDetail(userId) });
  } catch (error) {
    console.error(`Failed to fetch progress for user ${userId}: ${error}`);
  }
};

function fetchDetail(id) {
  // Your existing database logic to fetch the user's specific batch progress
}

Key Changes Explained #

1. User-Socket Mapping: The userSocketMap ensures we track exactly which socket belongs to which user—no more overwriting global variables.
2. Scoped Interval: Each user gets their own interval that only sends progress to their socket, using their unique userId to fetch the right data.
3. Cleanup on Disconnect: We remove the user from the map and clear their interval when they disconnect to prevent memory leaks and unnecessary API calls.
4. Consistent Event Name: Using a fixed event name like "batch-download-progress" makes it easier for your frontend to listen for updates without dealing with dynamic socket IDs.

Quick Note on Auth #

Make sure your Socket.io setup is integrated with your auth middleware so req.user.id is available when a socket connects. If you're using Express with Socket.io, you can use middleware to pass the authenticated user's info into the socket handshake.

内容的提问来源于stack exchange，提问作者r.k