Home > Article > Web Front-end > Implement routing function in nodejs_node.js
When I first started learning Node, I discovered a situation that was completely different from my previous views - what is JavaScript used for in your eyes? Special effects? or just interaction with the client? It can be said that JavaScript first ran in the browser. However, if you think about it this way, the browser just provides you with a context (context), which defines what can be done using JavaScript. It can be thought of as a similar enterprise. It defines what you can do here, but doesn't say much about what the JavaScript language itself can do. In fact, as a complete language, JavaScript can be used in different contexts and reflect different capabilities. The Nodejs mentioned here actually provides a context, a running environment, which allows JavaScript code to be run on the backend (out of the browser environment).
The core of routing selection is routing. As the name suggests, routing means that we have different processing methods for different URLs, such as processing the business logic of /start and processing the business of /upload module; the logic is inconsistent. In a realistic implementation, the routing process will "end" in the routing module, and the routing module is not the module that actually "takes action" on the request, otherwise it will not be available when our application becomes more complex. Nice extension.
Here we first create a module called requestHandlers and add a placeholder function to each request handler:
In this way, we can connect the request handler and the routing module so that the routing "has a path to follow". After that, we determined that a series of request handlers will be passed through an object, and this object needs to be injected into the router() function using a loose coupling method. The main file index.js:
As shown above, mapping different URLs to the same request handler is easy: just add a property with the key "/" to the object corresponding to requestHandlers.start. In this way, we can simply configure that requests for /start and / are handled by the start handler. After completing the definition of the object, we pass it to the server as an additional parameter, see server.js:
Copy code