入门Web开发者求教：这段Node.js listen函数功能及与普通服务器的差异

Hey there! Let's break down this Node.js code and answer your questions in plain terms.

This is a wrapped listen method that sets up an HTTP server with specialized request handling:

• First, it checks if the provided port is a number. If not, it triggers the passed callback with an error stating the port isn't a valid number.
• If the port is valid, it creates an HTTP server using Node's built-in http.createServer.
• The server routes requests based on their HTTP method:
  • For GET requests: It runs parseGetRequest (likely to parse URL query parameters) first, then uses an eventEmitter to fire an httpGetRequest event, passing along the request (req) and response (res) objects.
  • For POST requests: Similar to GET, it runs parsePostRequest (probably parsing the request body data) then emits an httpPostRequest event with req and res.
  • For any other HTTP methods (like PUT, DELETE), it simply sets req.parameters = null and doesn’t do further processing.
• Finally, it starts the server listening on the specified port.

Let’s compare it to a standard bare-bones server setup:

const http = require('http');
http.createServer((req, res) => {
  // All request handling logic lives directly here
  res.end('Hello World!');
}).listen(3000);

The key differences are:

• Event-driven decoupling: Instead of cramming all request-handling logic into the server callback, this code uses an event emitter to pass parsed requests to other parts of your app. Other modules can listen for httpGetRequest or httpPostRequest events and handle business logic there, keeping your server setup clean and separating concerns.
• Pre-parsed requests: It automatically handles parsing for GET and POST requests before emitting events. With a basic server, you’d have to write that parsing logic (or use a library) every time you handle those request types.
• Input validation: It adds a check to ensure the port is a number, returning an error via the callback if it’s not. Basic setups usually skip this kind of validation unless you add it manually.
• Scalable method handling: If you later want to add support for PUT or DELETE requests, you just add a new branch in this listen method to parse and emit a corresponding event. With a basic server, you’d have to modify the core server callback, which can get messy as your app grows.

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