Http request processing method and device

By implanting the core objects of Spring MVC module in the Netty server and combining Netty and Spring MVC to process Http requests, the problem of traditional php-fpm's performance consumption under high concurrent requests is solved, and efficient Http request processing and system are realized Performance improvement.

CN111444449BActive Publication Date: 2024-11-26BEIJING QIHOOD TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201811614132.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-12-27
Publication Date
2024-11-26
Estimated Expiration
2038-12-27

AI Technical Summary

Technical Problem

The traditional php-fpm model consumes a lot of system performance under high concurrency requests, and process creation is limited by operating system resources and cannot meet high concurrency requirements.

Method used

When receiving Http requests on the Netty-based server, the threads are allocated through the thread pool, and the core objects of the Spring MVC module are implanted in the data transmission channel. The combination of Netty and Spring MVC is used to process Http requests to achieve high concurrency and hierarchy deal with.

Benefits of technology

It improves the efficiency and system performance of Http request processing, supports high concurrent requests, and simplifies server maintenance and updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111444449B_ABST
    Figure CN111444449B_ABST
Patent Text Reader

Abstract

The present invention provides an Http request processing method and device, which is applied to a server built based on Netty, and the method includes: receiving an Http request from a client, and allocating a processing thread for the Http request through a thread pool of the server; initializing a data transmission channel of the server and a data pipeline for processing transmission data in the data transmission channel; implanting a core object of a Spring MVC module in the data channel; receiving and processing the Http request in the processing thread through a data pipeline implanted with the core object of the Spring MVC module, and transmitting the processing result back to the client through the data transmission channel. The method provided by the present invention can not only process high-concurrency Http requests based on Netty, but also perform hierarchical processing on Http requests based on the Spring MVC module, so that the processing of Http requests is clearer and is conducive to the maintenance and update of the server in the later stage.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a Http request processing method and device. Background Art

[0002] In traditional web development, php's nginx+fpm is often used to implement third-party interfaces to handle HTTP requests. php-fpm: It is a master + multiple child process model. A fastcgi process must be created for each request. The overhead of this process is very high in terms of system performance consumption under high concurrent requests. And processes cannot be created indefinitely because they are limited by the resource allocation and scheduling of the operating system itself. Generally speaking, the QPS of a single machine is about 100, which is very low and cannot meet high concurrent requirements.

[0003] Figure 1 The following figure shows the php-fpm process management diagram. Figure 1 The Application 1 to Application 4 shown in the figure can be php-fpm processes, which can distribute multiple work processes for multi-request web servers. Because each process is created dynamically, server performance will be consumed when each process is created. Summary of the invention

[0004] The present invention provides an Http request processing method and device to overcome the above problems or at least partially solve the above problems.

[0005] According to one aspect of the present invention, there is provided an Http request processing method, which is applied to a server built based on Netty, and the method comprises:

[0006] Receive an Http request from a client, and allocate a processing thread to the Http request through a thread pool on the server side;

[0007] Initialize the data transmission channel of the server and the data pipeline for processing the transmission data in the data transmission channel;

[0008] Implant the core object of the Spring MVC module in the data channel;

[0009] The Http request in the processing thread is received and processed through the data pipeline of the core object implanted in the Spring MVC module, and the processing result is transmitted back to the client through the data transmission channel.

[0010] Optionally, initializing a data transmission channel of the server and a data pipeline for processing transmission data in the data transmission channel includes:

[0011] Create a custom Netty data channel initializer;

[0012] Based on the initializer, the data transmission channel of the server is initialized and the data pipeline for processing the transmission data in the data transmission channel is processed, so as to provide a host container for the Spring MVC module.

[0013] Optionally, before the core object of the SpringMVC framework is implanted in the data channel, the method further includes:

[0014] Create the core objects of the SpringMVC module based on Servlet.

[0015] Optionally, the implanting of the core object of SpringMVC in the data channel includes:

[0016] The core object of the SpringMVC is set in the data pipeline that processes the transmission data in the data transmission channel.

[0017] Optionally, receiving and processing the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module, and transmitting the processing result back to the client through the data transmission channel, includes:

[0018] Receive the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module;

[0019] Scheduling the chain processor built into the data pipeline to process the Http request;

[0020] The processing result is submitted to the data transmission channel, and the data transmission channel transmits it back to the client.

[0021] Optionally, the chain processor built into the scheduling processes the Http request, including:

[0022] Acquire parameter information from the Http request, and adapt the parameter information to the Servlet request of the Spring MVC module;

[0023] After the Servlet receives the adapted Servlet request, a preset function method in the Servlet is started to process the Servlet request.

[0024] According to another aspect of the present invention, there is also provided an Http request processing device, which is applied to a server built based on Netty, and the device comprises:

[0025] A receiving module is configured to receive an Http request from a client and allocate a processing thread to the Http request through a thread pool of a server;

[0026] An initialization module, configured to initialize the data transmission channel of the server and a data pipeline for processing transmission data in the data transmission channel;

[0027] An implantation module configured to implant a core object of a Spring MVC module in the data channel;

[0028] The processing module is configured to receive and process the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module, and transmit the processing result back to the client through the data transmission channel.

[0029] Optionally, the initialization module is further configured to:

[0030] Create a custom Netty data channel initializer;

[0031] Based on the initializer, the data transmission channel of the server is initialized and the data pipeline for processing the transmission data in the data transmission channel is processed, so as to provide a host container for the Spring MVC module.

[0032] Optionally, the device further comprises:

[0033] Create a module and configure it to create the core objects of the SpringMVC module based on Servlet.

[0034] Optionally, the implant module is further configured to:

[0035] The core object of the SpringMVC is set in the data pipeline that processes the transmission data in the data transmission channel.

[0036] Optionally, the processing module is further configured to:

[0037] Receive the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module;

[0038] Scheduling the chain processor built into the data pipeline to process the Http request;

[0039] The processing result is submitted to the data transmission channel, and the data transmission channel transmits it back to the client.

[0040] Optionally, the processing module is further configured to:

[0041] Acquire parameter information from the Http request, and adapt the parameter information to the Servlet request of the Spring MVC module;

[0042] After the Servlet receives the adapted Servlet request, a preset function method in the Servlet is started to process the Servlet request.

[0043] According to another aspect of the present invention, a computer storage medium is provided, wherein the computer storage medium stores a computer program code. When the computer program code runs on a computing device, the computing device is caused to execute any of the above-mentioned Http request processing methods.

[0044] According to another aspect of the present invention, there is further provided a computing device, comprising:

[0045] processor;

[0046] a memory storing computer program code;

[0047] When the computer program code is executed by the processor, the computing device is caused to execute any one of the above-mentioned Http request processing methods.

[0048] The present invention provides an efficient Http request processing method and device. In the method provided by the present invention, after receiving the Http request from the client, the server built based on Netty first allocates a processing thread based on Netty, and implants the core object of the Spring MVC module when initializing the data transmission channel, and then processes the Http request through the Spring MVC module implanted in Netty. The method provided by the present invention can not only process high-concurrency Http requests based on Netty, but also perform hierarchical processing on Http requests based on the Spring MVC module, so that the processing of Http requests is clearer and is conducive to the maintenance and update of the server in the later stage.

[0049] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below.

[0050] Based on the following detailed description of specific embodiments of the present invention in conjunction with the accompanying drawings, those skilled in the art will become more aware of the above and other objects, advantages and features of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0052] Figure 1 This is a schematic diagram of php-fpm process management;

[0053] Figure 2 This is a flow chart of a method for processing an Http request according to an embodiment of the present invention;

[0054] Figure 3 It is a schematic diagram of the process of implanting the Spring MVC module in Netty according to an embodiment of the present invention;

[0055] Figure 4 It is a schematic diagram of the structure of an Http request processing device according to an embodiment of the present invention;

[0056] Figure 5 It is a schematic diagram of the structure of an Http request processing device according to a preferred embodiment of the present invention. DETAILED DESCRIPTION

[0057] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0058] Figure 2 is a flow chart of an Http request processing method according to an embodiment of the present invention, which is applied to a server built on Netty, such as Figure 2 As shown, the Http request processing method provided by the embodiment of the present invention may include:

[0059] Step S202, receiving an Http request from a client, and assigning a processing thread to the Http request through a thread pool on the server side;

[0060] Step S204, initializing the data transmission channel of the server and the data pipeline for processing the transmission data in the data transmission channel;

[0061] Step S206, implanting the core object of the Spring MVC module into the data channel;

[0062] Step S208, receiving and processing the Http request in the above processing thread through the data pipeline of the core object implanted in the Spring MVC module, and transmitting the processing result back to the client through the data transmission channel.

[0063] The embodiment of the present invention provides an efficient Http request processing method. After receiving the Http request from the client, the server built based on Netty first allocates a processing thread based on Netty, and implants the core object of the Spring MVC module when initializing the data transmission channel, and then processes the Http request through the Spring MVC module implanted in Netty. The method provided by the embodiment of the present invention can not only process high-concurrency Http requests based on Netty, but also perform hierarchical processing on Http requests based on the Spring MVC module, so that the processing of Http requests is clearer and is conducive to the maintenance and update of the server in the later stage.

[0064] Netty, as a Java open source framework, provides an asynchronous, event-driven network application framework and tools for rapid development of high-performance, highly reliable network servers and client programs. Netty itself is a framework based on non-blocking IO, with the characteristics of high concurrency, fast transmission and good encapsulation.

[0065] SpringMVC is a module in Spring Framework designed specifically for web applications. It provides convenient routing management, annotation configuration, and uses Spring IOC container to manage beans. Spring MVC is a layered Java web development framework. The MVC model provides a layered architecture in which each layer abstracts other layers, as follows:

[0066] 1. Model: The representation of domain-specific information used by the application

[0067] 2. View: The representation of the domain model (through the use of user interface elements such as input elements and buttons, which interact with the model).

[0068] 3. Controller: Mainly responsible for interpreting the user's input and converting it into a model, and then displaying the converted results to the user.

[0069] The embodiment of the present invention uses Netty to execute the process and customizes the Netty data transmission channel of the Spring MVC environment at the same time, so that the current Netty data transmission channel based on the Spring MVC environment can directly build an application based on Spring MVC, achieving the integration of the advantages of Netty and Spring MVC.

[0070] The above step S204 mentioned that after the processing thread is assigned to the Http request, the data transmission channel of the server and the data pipeline for processing the transmission data in the data transmission channel will be initialized. Specifically, a custom Netty data channel initializer can be created; based on the initializer, the data transmission channel of the server and the data pipeline for processing the transmission data in the data transmission channel are initialized, a host container is provided for the Spring MVC module, and then the core object of the SpringMVC module is implanted in the data channel.

[0071] Before the core object of the Spring MVC module is implanted in the data channel in the above step S206, the core object of the Spring MVC module needs to be created based on the Servlet, and then the core object of the Spring MVC is set to the data pipeline for processing the transmission data in the data transmission channel. The core object of the Spring MVC module may include: ApplicationContext. With this ApplicationContext object, all components of Spring MVC have a living environment. All objects required by Spring MVC itself are stored in this ApplicationContext. In addition, after creating the core object ApplicationContext, in order to enable the development characteristics of Spring MVC itself to be used in Netty, it is necessary to adapt Servlet on the basis of Netty. At this time, it is also necessary to create ServletContext and ServletConfig, which are necessary objects in the Servlet specification. With the objects related to Servlet, the ApplicationContext of Spring MVC can play a role, so that the high concurrency characteristics of Netty can be combined with the convenient development characteristics of Spring MVC.

[0072] In an embodiment of the present invention, the data pipeline in Netty is composed of multiple chain processors, each of which is responsible for processing specific business logic, and multiple processors are combined through the responsibility chain mode to process the entire business logic. Therefore, the above step S208 can also include: receiving the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module; scheduling the built-in chain processor in the data pipeline to process the above Http request; submitting the processing result to the data transmission channel, and the data transmission channel is returned to the client. Since the embodiment of the present invention mainly processes the Http request based on the Spring MVC module, when the built-in chain processor in the scheduling data pipeline processes the Http request, parameter information can be obtained from the Http request, and the above parameter information can be adapted to the Servlet request of the Spring MVC module; after the Servlet is passed in to the Servlet, the preset function method in the Servlet is started to process the Servlet request. Among them, the parameter information can include parameter information such as uri, Http request header information, and post parameter information of the Http request.

[0073] Figure 3 is a schematic diagram of the process of implanting the Spring MVC module in Netty according to an embodiment of the present invention, see Figure 3 It can be seen that the method may include:

[0074] S1, the Http request initiates a request to the Netty-based web server, and the EventLoopGroup in Netty allocates an available EventLoop for the current Http request;

[0075] S2, EventLoopGroup initializes a data transmission channel Channel and a data pipeline ChannelPipeline that processes the data transmitted in this Channel; ChannelPipeline is composed of multiple Handlers, each of which is responsible for processing specific business logic. Multiple Handlers are combined through the responsibility chain mode to process the entire business logic; when initializing Channel, the allocated EventLoop is obtained and bound to Channel; in the process of initializing ChannelPipeline, the core objects of Servlet+Spring MVC are implanted, and finally this ChannelPipeline is associated with the data transmission channel channel;

[0076] S3, Channel delivers the data in the Http request to ChannelPipeline for data processing;

[0077] S4, ChannelPipeline will schedule the chain processor (i.e. Handler 1 to Handler N) that processes the data transmitted in the current Channel to process the data;

[0078] S5: After the chain processor in ChannelPipeline completes the processing, it returns the processing result to Channel and transmits it back to the client.

[0079] The embodiment of the present invention also provides a method for initializing a NettyChannelPipeline with a Servlet+Spring MVC environment, which may include:

[0080] S2-1, create a Servlet+Spring MVC environment and set it to the DispatcherServletChannelInitializer object; specifically, it may include: first, simulate and generate a ServletContext object to provide a host container for Spring MVC; second, create the core object of Spring MVC, ApplicationContext, and set the corresponding ServletContext and ServletConfig objects; finally, set the core object of Spring MVC to Netty's ChannelPipeline to complete the configuration of ChannelPipeline, called DispatcherServletChannelInitializer, so as to better utilize Spring MVC's convenient business routing management and many other features;

[0081] In this embodiment, a custom Netty channel initializer ChannelInitializer needs to be created first. The name of the initialized ChannelInitializer is DispatcherServletChannelInitializer. In the construction method of this object, three objects, ServletContext, ServletConfig and ApplicationContext, need to be constructed to adapt the final Servlet request. The code is as follows:

[0082] MockServletContext servletContex=new MockServletContext();

[0083] MockServletConfig servletConfig=

[0084] new MockServletConfig(servletContext);

[0085] AnnotationConfigWebApplicationContextwac=

[0086] new AnnotationConfigWebApplicationContext();

[0087] wac.setServletContext(servletContext);

[0088] wac.setServletConfig(servletConfig);

[0089] wac.register(AppConfig.class)

[0090] wac.refresh();

[0091] After creating the environment required by Servlet+Spring MVC, the generated objects will be stored in the member variables of this class for later processing of Http requests;

[0092] this.dispatcherServlet=new DispatcherServlet(wac);

[0093] this.dispatcherServlet.init(servletConfig);

[0094] In the embodiment of the present invention, when initializing the data channel, the ChannelPipeline of its own business logic is first obtained through the Channel, and then the Handler for specifically processing the business in the ChannelPipeline is created and processed, that is, the ServletNettyHandler;

[0095] pipiline.addLast("Handler",new ServletNettyHandler(this.dispatcherServelet))

[0096] S2-2, complete the processing logic of the Handler in ChannelPipeline for the calling process of Servlet+Spring MVC, and determine the ServletNettyHandler that can make the request; implement the logical unit ChannelPipeline for real business processing, in which the built-in processor is ServletNettyHandler, and the method responsible for reading the Http request data is channelRead0(); the specific methods may include:

[0097] S2-2-1, obtain URI and other information from Netty's HTTP request, and adapt it to Spring MVC's Servlet request, that is, convert Netty's Http request into the format of the Http request required by the Servlet;

[0098] First, fill in the basic information of Servlet Request: assign the uri, pathinfo and method of FullHttpRequest (Netty's request) to ServletRequest;

[0099] Secondly, fill in the data information of Servlet Request and fill the data in NettyRequest into ServletRequest;

[0100] S2-2-2, passes the adapted Servlet request to the Servlet, starts the Servlet's "service()" method to process the request, and returns the result to Netty's data channel Channel.

[0101] Call the service method of the Servlet created in the initialization of DispatcherServletChannelinitializer, and pass the Http request of the Servlet adapted in S3-2-1 to the service method of the Servlet, process the request, and finally return the Http Response of the Servlet;

[0102] this.servlet.service(servletRequest, servletResponse)

[0103] S2-2-3, adapt the Servlet's Http Response to Netty's Response;

[0104] S2-2-4, write Netty's Http Response into the Context of ChannelHandler, which means that the response processed by SpringMVC+Servlet is transmitted back to Netty's Channel and finally returned to the client.

[0105] S2-3, finally add the custom DispatcherServletChannelInitializer to the Netty initialization list, thus completing the integration of Netty and SpringMVC.

[0106] childHandler(new DispatcherServletChannelInitializer())

[0107] The method provided by the embodiment of the present invention will not change due to the increase of business logic, and only needs to be integrated once. When a new business logic comes, it is still developed in the way of Spring MVC. The whole process is still developed in the way of Spring MVC. The user does not perceive the existence of Netty at all, but the network efficiency is greatly improved because of Netty.

[0108] Based on the same inventive concept, the embodiment of the present invention also provides an Http request processing device, which is applied to a server built based on Netty, such as Figure 4 As shown, the Http request processing device provided by the embodiment of the present invention may include:

[0109] The receiving module 410 is configured to receive an Http request from a client and allocate a processing thread to the Http request through a thread pool of a server;

[0110] An initialization module 420, configured to initialize a data transmission channel of the server and a data pipeline for processing transmission data in the data transmission channel;

[0111] An implantation module 430 is configured to implant a core object of a Spring MVC module in a data channel;

[0112] The processing module 440 is configured to receive and process the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module, and transmit the processing result back to the client through the data transmission channel.

[0113] In a preferred embodiment of the present invention, the initialization module 420 may also be configured as follows:

[0114] Create a custom Netty data channel initializer;

[0115] Based on the initializer, the server-side data transmission channel is initialized and the data pipeline that processes the transmission data in the data transmission channel is processed, providing a host container for the Spring MVC module.

[0116] In a preferred embodiment of the present invention, Figure 5 As shown, the above embodiment may further include:

[0117] The creation module 450 is configured to create the core object of the SpringMVC module based on the Servlet.

[0118] In a preferred embodiment of the present invention, the implant module 430 may also be configured as:

[0119] Set the core objects of SpringMVC to the data pipeline that handles the transmission of data in the data transmission channel.

[0120] In a preferred embodiment of the present invention, the processing module 440 may also be configured as follows:

[0121] Receive the Http request in the processing thread through the data pipeline of the core object implanted in the Spring MVC module;

[0122] Schedule the built-in chain processor in the data pipeline to process HTTP requests;

[0123] The processing results are submitted to the data transmission channel, which then transmits them back to the client.

[0124] In a preferred embodiment of the present invention, the processing module 440 may also be configured as follows:

[0125] Get parameter information from the Http request and adapt the above parameter information to the Servlet request of the Spring MVC module;

[0126] After the Servlet request is adapted and passed to the Servlet, the preset function method in the Servlet is started to process the Servlet request.

[0127] Based on the same inventive concept, an embodiment of the present invention further provides a computer storage medium, which stores computer program code. When the computer program code runs on a computing device, the computing device executes the Http request processing method described in any of the above embodiments.

[0128] Based on the same inventive concept, an embodiment of the present invention further provides a computing device, including:

[0129] processor;

[0130] a memory storing computer program code;

[0131] When the computer program code is executed by the processor, the computing device is caused to execute the Http request processing method described in any of the above embodiments.

[0132] The present invention provides an efficient Http request processing method and device. Based on the solution provided by the embodiment of the present invention, by analyzing the operating principles of Netty and SpringMVC, through the Netty execution process, and at the same time personalizing the Netty data transmission channel of the SpringMVC environment, the current Netty data transmission channel based on the Spring MVC environment can directly build an application based on Spring MVC, effectively integrating the two frameworks, not only utilizing the efficient network communication of Netty, but also using the convenient properties of Spring MVC in this efficient network communication, while improving the Http request processing efficiency, but also greatly improving the development efficiency of high-concurrency data interfaces based on the Java technology stack.

[0133] Those skilled in the art can clearly understand that the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments, and for the sake of brevity, they are not further described here.

[0134] In addition, the functional units in various embodiments of the present invention may be physically independent of each other, or two or more functional units may be integrated together, or all functional units may be integrated into one processing unit. The above integrated functional units may be implemented in the form of hardware, or in the form of software or firmware.

[0135] Those skilled in the art can understand that if the integrated functional unit is implemented in the form of software and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention can essentially or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, which includes a number of instructions to enable a computing device (such as a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention when running the instructions. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

[0136] Alternatively, all or part of the steps of implementing the aforementioned method embodiments may be accomplished by hardware associated with program instructions (such as a computing device such as a personal computer, a server, or a network device), and the program instructions may be stored in a computer-readable storage medium. When the program instructions are executed by a processor of a computing device, the computing device executes all or part of the steps of the methods described in the embodiments of the present invention.

[0137] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that within the spirit and principles of the present invention, the technical solutions described in the aforementioned embodiments can still be modified, or some or all of the technical features therein can be replaced by equivalents. However, these modifications or replacements do not deviate from the protection scope of the present invention.

Claims

1. An Http request processing method, applied to a server built based on Netty, the method comprising: Receive an Http request from a client, and allocate a processing thread to the Http request through a thread pool on the server side; Initialize the data transmission channel of the server and the data pipeline for processing the transmission data in the data transmission channel; Implanting the core object of the SpringMVC module in the data transmission channel; Receive and process the Http request in the processing thread through the data pipeline of the core object implanted in the SpringMVC module, and transmit the processing result back to the client through the data transmission channel; The receiving and processing of the Http request in the processing thread through the data pipeline of the core object implanted in the SpringMVC module, and transmitting the processing result back to the client through the data transmission channel, includes: Receive the Http request in the processing thread through the data pipeline of the core object implanted in the SpringMVC module; Scheduling the chain processor built into the data pipeline to process the Http request; The processing result is submitted to the data transmission channel, and the data transmission channel transmits it back to the client.

2. The method according to claim 1, wherein: Initializing the data transmission channel of the server and processing the data pipeline of the transmission data in the data transmission channel, including: Create a custom Netty data channel initializer; Based on the initializer, the data transmission channel of the server is initialized and the data pipeline for processing the transmission data in the data transmission channel is processed, so as to provide a host container for the SpringMVC module.

3. The method according to claim 1, wherein: Before the core object of the SpringMVC framework is implanted in the data transmission channel, the method further includes: Create the core objects of the SpringMVC module based on Servlet.

4. The method according to claim 3, wherein: The core object of SpringMVC is implanted in the data transmission channel, including: The core object of the SpringMVC is set in the data pipeline that processes the transmission data in the data transmission channel.

5. The method according to claim 3, wherein: The scheduling of the built-in chain processor in the data pipeline to process the Http request includes: Acquire parameter information from the Http request, and adapt the parameter information to the Servlet request of the SpringMVC module; After the Servlet receives the adapted Servlet request, a preset function method in the Servlet is started to process the Servlet request.

6. An Http request processing device, applied to a server built based on Netty, the device comprising: A receiving module is configured to receive an Http request from a client and allocate a processing thread to the Http request through a thread pool of a server; An initialization module, configured to initialize the data transmission channel of the server and a data pipeline for processing transmission data in the data transmission channel; An implantation module configured to implant a core object of a SpringMVC module in the data transmission channel; A processing module is configured to receive and process the Http request in the processing thread through a data pipeline of a core object implanted in the SpringMVC module, and transmit the processing result back to the client through the data transmission channel; The processing module is further configured to: Receive the Http request in the processing thread through the data pipeline of the core object implanted in the SpringMVC module; Scheduling the chain processor built into the data pipeline to process the Http request; The processing result is submitted to the data transmission channel, and the data transmission channel transmits it back to the client.

7. The device according to claim 6, wherein: The initialization module is also configured as: Create a custom Netty data channel initializer; Based on the initializer, the data transmission channel of the server is initialized and the data pipeline for processing the transmission data in the data transmission channel is processed, so as to provide a host container for the SpringMVC module.

8. The device according to claim 6, wherein: Also includes: Create a module and configure it to create the core objects of the SpringMVC module based on Servlet.

9. The device according to claim 8, wherein: The implant module is also configured as: The core object of the SpringMVC is set in the data pipeline that processes the transmission data in the data transmission channel.

10. The device according to claim 9, wherein: The processing module is further configured to: Acquire parameter information from the Http request, and adapt the parameter information to the Servlet request of the SpringMVC module; After the Servlet receives the adapted Servlet request, a preset function method in the Servlet is started to process the Servlet request.

11. A computer storage medium storing a computer program code, wherein when the computer program code is executed on a computing device, the computing device is caused to execute the HTTP request processing method according to any one of claims 1 to 5.

12. A computing device comprising: processor; a memory storing computer program code; When the computer program code is executed by the processor, it causes the computing device to execute the HTTP request processing method according to any one of claims 1 to 5.