WO2014078989A1

WO2014078989A1 - Message processing method and server

Info

Publication number: WO2014078989A1
Application number: PCT/CN2012/084897
Authority: WO
Inventors: 李亿
Original assignee: 华为技术有限公司
Priority date: 2012-11-20
Filing date: 2012-11-20
Publication date: 2014-05-30
Also published as: CN103370917A; CN103370917B

Abstract

Embodiments of the present invention provide a message processing method and a server. The message processing method comprises: the server receiving a first request message sent by a client; according to property information of the first request message, determining a first operation event corresponding to the first request message; if the server has started to execute the first operation event, caching the first request message in a first cached message queue, wherein the first cached message queue is used to cache different request messages sent by different clients, and the server needs to execute the same first operation event for the different request messages sent by different clients in the first cached message queue; and when the server finishes executing the first operation event, the server sending a response message of the first operation event to each client corresponding to the different request messages in the first cached message queue, which reduces overheads of the server for processing the same operation event, and improves processing efficiency of the server.

Description

Message processing method and server

TECHNICAL FIELD Embodiments of the present invention relate to the Internet (Internet Technology, IT for short) technology, and in particular, to a message processing method and a server. Background technique

The IT system usually includes two types of communication entities, one is a client and the other is a server. The server usually provides services for multiple clients, and the client and the server establish a connection by sending and receiving messages.

Generally, the client sends a message to the server from time to time, so that the server performs a corresponding operation according to the message; accordingly, after receiving the message of the client, the server can process the message content to complete the processing of the message content. The processing result is returned to the corresponding client. When a large number of clients send messages to the server at the same time, the server will process the messages of these clients at the same time, which causes the server to have a large overhead, which affects the server's message processing efficiency, and may even have problems in accepting new client messages. Summary of the invention

The embodiment of the invention provides a message processing method and a server to solve the problem that the server has a large overhead when processing a large number of client messages.

A first aspect of the embodiments of the present invention provides a message processing method, including:

The server receives the first request message sent by the client;

Determining, by the server, the first operation event corresponding to the first request message according to the attribute information of the first request message;

Determining, by the server, whether the first operation event has been started, and if the first operation event has been started, buffering the first request message in the first cache message queue ij, the first cache message The queue is used to cache different request messages sent by different clients, and the server needs to perform the same first operation event for different request messages sent by different clients in the first cache message queue; When the server performs the first operation event, the server sends a response message of the first operation event to each client corresponding to the different request message in the first cache message queue.

In a first possible implementation manner of the first aspect, the determining, by the server, the first operation event corresponding to the first request message according to the attribute information of the first request message, Determining, by any one of the operation object, the operation content, or the operation result of the first request message, or any combination thereof, the first operation event corresponding to the first request message.

In a second possible implementation manner of the first aspect, if the server determines that the first operation event is not started, the method further includes:

Initiating execution of the first operational event and creating a first cached message queue corresponding to the first operational event.

With reference to the first aspect, the first possible implementation of the first aspect, and the second possible implementation manner of the first aspect, in a third possible implementation, the server The first request message is cached before the first cache message queue, and further includes: the server determining whether the first operation event is a preset merge processing event, and if yes, performing the first request message The step of caching in the first cache message queue; if not, the server initiating execution of the first operation event for the first request message.

In conjunction with the third possible implementation manner, in a fourth possible implementation manner, the preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency.

In conjunction with the fourth possible implementation manner, in a fifth possible implementation manner, the operation processing event that increases server CPU processing time and efficiency includes at least one of the following operational events:

Add operation, create operation, delete operation, modify operation, query operation, restart operation, backup operation, start operation, stop operation.

With reference to the first aspect, the first possible implementation manner of the first aspect, the second possible implementation manner of the first aspect, and any possible implementation manner of the third possible implementation manner, In an implementation manner, after all the clients corresponding to all the request messages in the first cache message queue send the response message of the first operation event, the method further includes: Deleting the first cached message queue.

A second aspect of the embodiments of the present invention provides a server, including:

a receiving module, configured to receive a first request message sent by the client;

a determining module, configured to determine, according to the attribute information of the first request message, a first operation event corresponding to the first request message;

a processing module, configured to determine whether the first operation event has been started, and if the first operation event has been started, buffering the first request message in a first cache message queue, the first cache message The queue is used to cache different request messages sent by different clients, and the same first operation event needs to be performed for different request messages sent by different clients in the first cache message queue;

And a sending module, configured to send, when the first operation event is completed, a response message of the first operation event to each client corresponding to the different request message in the first cache message queue.

In a first possible implementation manner of the second aspect, the determining module is specifically configured to determine, according to any one of the operation object, the operation content, or the operation result of the first request message, or any combination thereof The first operation event corresponding to the first request message is described.

In a second possible implementation manner of the second aspect, the processing module is further configured to: after determining that the first operation event is not started, start to execute the first operation event, and create a corresponding operation The first cached message queue of the first operational event.

With reference to the second aspect, the first possible implementation manner of the second aspect, and the second possible implementation manner of the second aspect, in a third possible implementation manner, the method further includes:

a pre-processing module, configured to determine whether the first operation event is a preset merge processing event, and if yes, the processing module performs the step of buffering the first request message in a first cache message queue; If no, the processing module initiates execution of the first operational event for the first request message.

In combination with the fourth possible implementation manner, in the fifth possible implementation manner, the adding The operation processing event of the server CPU processing time and efficiency includes at least one of the following operational events:

With reference to the second aspect, the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, any possible implementation manner of the third possible implementation manner, possible in the sixth In the implementation, it also includes:

And a deleting module, configured to delete the first cached message queue after the sending module sends the response message of the first operation event to all clients corresponding to all the request messages in the first cache message queue.

A third aspect of the embodiments of the present invention provides a server, including:

a receiver, configured to receive a first request message sent by the client;

a processor, configured to determine, according to the attribute information of the first request message, a first operation event corresponding to the first request message, determine whether the first operation event has been started, and if the first operation event has been started An operation event, the first request message is cached in a first cache message queue, and the first cache message queue is used to cache different request messages sent by different clients, for different clients in the first cached message queue. Different request messages sent by the terminal need to perform the same first operation event;

And a transmitter, configured to send, when the first operation event is completed, a response message of the first operation event to each client corresponding to a different request message in the first cache message queue.

In a first possible implementation manner of the third aspect, the processor is specifically configured to determine, according to any one of an operation object, an operation content, or an operation result of the first request message, or any combination thereof. The first operation event corresponding to the first request message is described.

In a second possible implementation manner of the third aspect, the processor is further configured to, after determining that the first operation event is not started, start to execute the first operation event, and create a corresponding to the The first cached message queue of the first operational event.

With reference to the third aspect, the first possible implementation manner of the third aspect, and the second possible implementation manner of the third aspect, in a third possible implementation manner, the processor Also used to determine whether the first operational event is a preset merge processing event, such as If yes, performing the step of buffering the first request message in the first cache message queue; if not, initiating execution of the first operation event for the first request message.

With reference to the third aspect, the first possible implementation manner of the third aspect, the second possible implementation manner of the third aspect, and any possible implementation manner of the third possible implementation manner, where possible in the sixth In an implementation manner, the processor is further configured to delete the first message after the sender sends the response message of the first operation event to all clients corresponding to all the request messages in the first cache message queue. A cached message queue.

A fourth aspect of the embodiments of the present invention provides a server, including:

a processor, a communication interface, and a memory;

The communication interface is configured to receive a request message of the client and output a response message to the client; the processor is configured to execute a program; the memory is configured to store a program; and the program is configured to receive a communication interface to forward Determining, by the first request message of the client, the first operation event corresponding to the first request message according to the attribute information of the first request message; determining whether the first operation event has been started, if the execution has already started The first operation event, the first request message is cached in a first cache message queue, and the first cache message queue is used to cache different request messages sent by different clients, where the server is for the first cache Different request messages sent by different clients in the message queue need to perform the same first operation event; when the server finishes executing the first operation event, corresponding to different request messages in the first cache message queue Each client sends a response message for the first operational event.

In a first possible implementation manner of the fourth aspect, the program is further configured to: if it is determined that the first operation event is not started, start executing the first operation event, and create a pair The first cached message queue should be in the first operational event.

In a second possible implementation manner of the fourth aspect, the program is further configured to: determine, according to any one of an operation object, an operation content, or an operation result of the first request message, or any combination thereof The first operation event corresponding to the first request message.

With reference to the fourth aspect, the first possible implementation manner of the fourth aspect, and the second possible implementation manner of the fourth aspect, in a third possible implementation, the program is further And, after determining that the first operation event is not started, starting to execute the first operation event, and creating a first cache message queue 1 corresponding to the first operation event.

In conjunction with the third possible implementation, in a fourth possible implementation, the program is further configured to: determine whether the first operation event is a preset merge processing event, and if yes, execute the The step of buffering the first request message in the first cache message queue; if not, initiating execution of the first operation event for the first request message.

With reference to the fourth aspect, the first possible implementation manner of the fourth aspect, the second possible implementation manner of the fourth aspect, and any possible implementation manner of the third possible implementation manner, where possible in the sixth In an implementation manner, the program is further configured to delete the first message after the communication interface sends the response message of the first operation event to all clients corresponding to all the request messages in the first cache message queue. Cache message queues.

The message processing method and the server of the embodiment of the present invention obtain the response message of the first operation event by performing processing on the first operation event corresponding to the first request message, and send the response message to the storage to perform the same first operation. Each client corresponding to a different request message in the first cache message queue of the different request message of the event, therefore, the server only needs to perform processing for the first operation event corresponding to the multiple clients, thereby reducing server processing The overhead of the same operational events improves the processing efficiency of the server, enabling the server to receive and process more client messages. DRAWINGS

The drawings used in the embodiments or the description of the prior art are briefly introduced. It is obvious that the drawings in the following description are some embodiments of the present invention, and are not creative to those skilled in the art. Other drawings can also be obtained from these drawings on the premise of labor.

1 is a flowchart of Embodiment 1 of a message processing method according to the present invention;

2 is a flowchart of Embodiment 2 of a message processing method according to the present invention;

3 is a schematic structural diagram of Embodiment 1 of a server according to the present invention;

4 is a schematic structural diagram of Embodiment 2 of a server according to the present invention;

FIG. 5 is a schematic structural diagram of Embodiment 3 of a server according to the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

1 is a flowchart of a first embodiment of a message processing method according to the present invention. As shown in FIG. 1, the message processing method in this embodiment may include:

101. The server receives a first request message sent by the client.

Specifically, the server may receive a request message sent to the client by at least one client, the first request message being one of the request messages received by the server.

It can be understood that the first request message is a request message of any event that can be processed by the client requesting the server.

102. The server determines, according to the attribute information of the first request message, a first operation event corresponding to the first request message.

Specifically, the server may determine, according to the attribute information included in the first request message, that the first request message requests the server to perform an operation, that is, determine the first operation event.

The attribute information may be, for example, an operation content and an operation object included in the first request message. For example, if the operation object included in the first request message is a server information list, and the operation content is a query, according to the operation object and the operation content, the first request message requesting server may perform the "query server information list" operation, That is, the first operation event is "Query Server Information List".

103. The server determines whether it has started to execute the first operation event.

Specifically, for example, the server may determine whether the operation currently being executed contains the same operation event as the first operation event by querying its own maintenance list or the like.

104. If the first operation event has been started, the first request message is cached in the first cache message queue, and the first cache message queue is used to cache different request messages sent by different clients, where the server is in the first cached message queue. Different request messages sent by different clients need to perform the same first operational event.

Specifically, if the query server determines that there is processing for the first operation event in the operation currently being processed, the server puts the first request message into the first cache message queue and waits for the first operation event requested by the server. As a result, the first cache message queue is a cache area set by the server, and is used to store different request messages sent by different clients to the server requesting the server to perform the same first operation event. That is, from the start of the first operation event by the server, until the server executes the first operation event, all the request messages received by the server to execute the first operation event are placed in the first cache message queue to wait for the server. The result of processing the first operational event.

105. When the server finishes performing the first operation event, the server sends a response message of the first operation event to each client corresponding to the different request message in the first cache message queue.

Specifically, after the server processes the first operation event, acquiring, from the first cache message queue, the corresponding at least one client identifier of the at least one request message stored in the first cache message queue, and the first A response message to the operational event is sent to the corresponding client identified by the at least one client.

In the message processing method of the embodiment, the response message of the first operation event is obtained by performing processing on the first operation event corresponding to the first request message, and the response message is sent to the storage to perform the same first operation event. Each client corresponding to a different request message in the first cache message queue of the request message, therefore, the server only needs to perform processing for the first operation event corresponding to the multiple clients, thereby reducing the server processing the same operation event. of Overhead, improve the processing efficiency of the server, enabling the server to receive and process more client messages.

Further, if the server determines that it has not started executing the first operation event, it starts executing the first operation event and creates a first cache message queue corresponding to the first operation event.

Specifically, the server may determine, according to any one of the operation object, the operation content, or the operation result of the first request message, or any combination thereof, the first operation event corresponding to the first request message, if the server determines according to the attribute information. The operation event, that is, the first operation event does not start execution, the server starts executing the first operation event, and creates a queue, that is, the first cache message queue, to store the first request message.

Further, the server caches the first request message before the first cache message queue, and the server may further determine whether the first operation event is a preset merge processing event, and if yes, execute the The step of the first request message being cached in the first cache message queue; if not, the server initiating execution of the first operation event for the first request message.

Specifically, the server caches the first request message before the first cache message queue, and further determines whether the first operation event corresponding to the first request message is a preset merge processing event by searching corresponding record information, where the Set merge processing events include, but are not limited to, operational processing events that increase server CPU processing time and efficiency.

For example, the operational processing event that increases server CPU processing time and efficiency includes at least one of the following operational events:

If the first operation event is a preset merge processing event, the first request message is cached in the first cache message queue, and if the first operation event is not a preset merge processing event, the server may start for the first request message. Execute the first operational event.

Specifically, for example, the "query A server" event is a preset merge processing event, and the "query current user number" event is a preset non-merging processing event, and the server learns the request message according to the attribute information of the received request message. If the corresponding operation event is a "query A server" event, the request message is cached in a cache queue that needs to execute the "query A server" event, and the server learns the request message according to the attribute information of the received request message. The corresponding operation event is the "query the current number of users" event, and the server executes the "query the current number of users" event, so that the server determines whether the received request is a preset merge processing event, and requests the server to execute the preset. The request message for merging the processing event is cached, and the request message for requesting the server to execute the non-preset merge processing event is directly processed, thereby improving the processing efficiency of the server, improving compatibility with the existing server, and facilitating operation.

Further, after the sending, by the client, the response message of the first operation event to all the clients corresponding to all the request messages in the first cache message queue, the method further includes: deleting the first cache message queue.

Specifically, after the server sends the response message of the first operation event to all the clients corresponding to all the request messages in the first cache message queue, the server may also delete the first cache message queue to avoid sending the first operation event. The response message is followed by a new first request message placed in the first cache message queue waiting for a response to the first operational event.

2 is a flowchart of a second embodiment of a message processing method according to the present invention. To describe the message processing method in the embodiment of the present invention, please refer to FIG. 2, and FIG. 2 is processed by a Hypertext Transfer Protocol (http) server. The request message sent by the http client is an example to explain the message processing method.

201. Receive a request message.

In 201, the message interaction module of the http server receives the request message sent by the http client, and the http client may be multiple.

202. Send a request message to the message management module.

In 202, the message interaction module of the http server sends the request message "get http: 〃 10.122.101.43:8080/hwm/server?name=namel" sent by the http client to the message management module of the http server.

203. Put the request message into the message queue.

In 203, the message management module learns that the request message is a query operation event by using an attribute of the request message, and the attribute of the request message is http://10.122.101.43: 8080/hwm/server, where the query name is namel, htt server By judging that the query operation event is a preset merge processing event, the message management module may further determine whether the processing module of the http server has started to execute the request message request. The query name is namel http://10.122.101.43:8080 /hwm/server" Query operation event, if the processing module is currently positive The operation management event does not have the operation, and the message management module creates a new message queue to store the request message. If the message management module determines that the operation operation event currently being executed by the processing module of the http server has the operation, the request message is placed. In the message queue corresponding to the message, the request sent by the http client in the message queue is http. The server performs the query operation of the query name name http://10.122.101.43:8080/hwm/server" The message of the event.

204. The notification message processing module processes the request message.

The message management module notifies the message processing module to process the first request message placed in the newly created message queue, and the message management module can also notify the message processing module to process the request message with the highest priority level in the newly created message queue.

205. Process the request message.

The message processing module processes the query operation name for the query name name http://10.122.101.43 :8080/hwm/server.

206. Return the result of the request message processing.

The processing module notifies the message management module of the response to the query operation event of the query name http_10.122.101.43: 8080/hwm/server.

207. Obtain client information.

The message management module obtains the client information of all the request messages from the message queue of the query request server http://10.122.101.43:8080/hwm/server query operation event.

208. The notification message interaction module returns the result of the request.

The message management module notifies the message interaction module to return the message processing module to all the obtained clients. The query name is http:〃10.122.101.43:8080/hwm/server, and the response message of the operation event is queried.

209. Return the result of the request.

The message interaction module returns the above response message to all of the above clients.

Further, after the message interaction module returns the foregoing response message to all the clients, the message management module may delete and store the query operation event corresponding to the query name http://10.122.101.43: 8080/hwm/server. The message queue for the request message. In addition, the message processing method in the embodiment of the present invention can also be applied to the Transmission Control Protocol/User Datagram Protocol (Tcp/udp) server to process the tcp/udp client to send to the Tcp/udp client. The message, the execution process, and the beneficial effects are similar to the second embodiment of the message processing method. For details, refer to the second embodiment of the message processing method, and details are not described herein again.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

3 is a schematic structural diagram of a first embodiment of a server according to the present invention. As shown in FIG. 3, the server in this embodiment includes: a receiving module 301, a determining module 302, a processing module 303, and a sending module 304, where the receiving module 301 is configured to Receiving a first request message sent by the client; the determining module 302, configured to determine, according to the attribute information of the first request message, a first operation event corresponding to the first request message, where the processing module 303 is configured to determine whether it is The first operation event has been started, and if the first operation event has been started, the first request message is cached in a first cache message queue, and the first cache message queue is used to cache different client sending Different request messages, the same first operation event needs to be executed for different request messages sent by different clients in the first cache message queue; the sending module 304 is configured to execute the first operation event when the first operation event is completed Sending, to each client corresponding to different request messages in the first cache message queue The response message of the first operational event.

The server of this embodiment may be used to implement the technical solution of the first embodiment of the message processing method, and the implementation principle and technical effects are similar, and details are not described herein again.

On the basis of the foregoing embodiment, the processing module 303 is further configured to: after determining that the first operation event is not started, start to execute the first operation event, and create a corresponding operation event. First cache message queue,

Further, the determining module 302 may be further configured to determine, according to any one of the operation object, the operation content, or the operation result of the first request message, or any combination thereof, the first request message The first operational event.

Further, the server of the embodiment of the present invention may further include a preprocessing module, a preprocessing module. a block, configured to determine, before the processing module 303 caches the first request message in the first cache message queue, whether the first operation event is a preset merge processing event, and if yes, the processing module 303: Perform the step of buffering the first request message in a first cache message queue; if not, the processing module 303 starts to execute the first operation event for the first request message.

Specifically, before the processing module 303 caches the first request message in the first cache message queue, the pre-processing module determines whether the first operation event corresponding to the first request message is a preset merge by searching corresponding record information. Processing the event, the preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency, and the operation processing event that increases server CPU processing time and efficiency includes at least one of the following operational events : Add operation, create operation, delete operation, modify operation, query operation, restart operation, backup operation, start operation, stop operation.

Further, on the basis of the foregoing embodiment, the server in the embodiment of the present invention may further include a deleting module, where the deleting module is used by all the clients corresponding to all the request messages in the first cached message queue in the sending module 304. After transmitting the response message of the first operation event, deleting the first cache message queue.

4 is a schematic structural diagram of a second embodiment of a server according to the present invention. As shown in FIG. 4, the server in this embodiment includes: a receiver 401, a processor 402, and a transmitter 403, where the receiver 401 is configured to receive a client. a first request message, where the processor 402 is configured to determine, according to the attribute information of the first request message, a first operation event corresponding to the first request message, and determine whether the first operation event has been started, If the first operation event has been started, the first request message is cached in a first cache message queue, and the first cache message queue is used to cache different request messages sent by different clients, for the first The different request messages sent by different clients in the cache message queue need to perform the same first operation event; the sender 403 is configured to: when the first operation event is completed, to the first cache message queue Each client corresponding to the different request message sends a response message of the first operation event.

Further, the processor 402 is further configured to determine that the self does not start to execute the first After an operation event, the first operation event is started to be executed, and a first cache message queue corresponding to the first operation event is created.

Further, the processor 402 is specifically configured to: if it is determined that the first operation event is not started, initiate execution of the first operation event, and create a first cache message queue corresponding to the first operation event.

Further, the processor 402 is further configured to determine whether the first operation event is a preset merge processing event, and if yes, perform the step of buffering the first request message in the first cache message queue. And if not, initiating execution of the first operational event for the first request message.

Specifically, the processor 402 caches the first request message before the first cache message queue, and determines whether the first operation event corresponding to the first request message is a preset merge processing event by searching corresponding record information. The preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency, and the operation processing event that increases server CPU processing time and efficiency includes at least one of the following operation events: Create operation, delete operation, modify operation, query operation, restart operation, backup operation, start operation, stop operation.

Further, the processor 402 may be further configured to delete the response message after the sender sends the response message of the first operation event to all clients corresponding to all the request messages in the first cache message queue. The first cached message queue.

FIG. 5 is a schematic structural diagram of Embodiment 3 of a server according to the present invention, as shown in FIG. 5, the server

500 includes:

a processor (Rocessor) 510, a communication interface 520, a memory 530, and a bus 540; wherein the processor 510, the communication interface 520, and the memory 530 are completed by the bus 540 Communication.

The communication interface 520 is configured to receive a request message of the client and output a response message to the client.

The processor 510 is configured to execute the program 511.

The memory 530 is configured to store the program 511.

Specifically, the program 511 can include program code, and the program code includes computer operation instructions. The processor 510 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

The memory 530 is used to store the program 511. Memory 530 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory. Program 511 can specifically include a piece of code.

The program 511 is configured to receive a first request message of the client that is forwarded by the communication interface, determine a first operation event corresponding to the first request message according to the attribute information of the first request message, and determine whether the user has started executing the first An operation event, if the first operation event has been started, the first request message is cached in a first cache message queue, and the first cache message queue is used to cache different request messages sent by different clients. The server needs to perform the same first operation event for different request messages sent by different clients in the first cache message queue; when the server finishes executing the first operation event, to the first cache Each client corresponding to a different request message in the message queue sends a response message of the first operation event.

Further, the program 511 is configured to, if it is determined that the first operation event is not started, start executing the first operation event, and create a first cache message queue corresponding to the first operation event.

Further, the program 511 is configured to determine, according to any one of the operation object, the operation content, or the operation result of the first request message, or any combination thereof, the first operation event corresponding to the first request message.

Further, the program 51 1 is configured to, after determining that the first operation event is not started, start to execute the first operation event, and create a first cache message queue corresponding to the first operation event.

Further, the program 511 is configured to: determine whether the first operation event is a preset merge processing event, and if yes, perform the step of buffering the first request message in a first cache message queue; if not, Executing the first operational event is initiated for the first request message. The preset merge processing event includes: an operation processing event that increases server CPU processing time and efficiency. The operation processing event for increasing server CPU processing time and efficiency includes at least one of the following operation events: an increase operation, a create operation, a delete operation, a modify operation, a query operation, a restart operation, a backup operation, a startup operation, a stop operation . Further, the program 51 1 is configured to delete the first cache after the communication interface sends the response message of the first operation event to all clients corresponding to all the request messages in the first cache message queue. message queue.

The server of the embodiment receives the first request message of the client through the communication interface, and the processor executes the program stored in the memory to perform processing on the first operation event corresponding to the first request message to obtain a response message of the first operation event, and The response message is sent to each client corresponding to the different request message in the first cache message queue of the different request message that needs to execute the same first operation event through the communication interface, and therefore, the server is corresponding to the multiple clients. The first operation event only needs to be processed once, thereby reducing the overhead of the server processing the same operation event, improving the processing efficiency of the server, and enabling the server to receive and process more client messages.

It should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

claims

1. A message processing method, characterized by including:

The server receives the first request message sent by the client;

The server determines the first operation event corresponding to the first request message according to the attribute information of the first request message;

The server determines whether it has started executing the first operation event. If it has started executing the first operation event, caches the first request message in a first cache message queue. The first cache message queue uses In order to cache different request messages sent by different clients, the server needs to execute the same first operation event for different request messages sent by different clients in the first cache message queue;

When the server completes executing the first operation event, the server sends a response message to the first operation event to each client corresponding to different request messages in the first cache message queue.

2. The method according to claim 1, characterized in that, the server determines the first operation event corresponding to the first request message according to the attribute information of the first request message, including: the server determines the first operation event corresponding to the first request message according to the attribute information of the first request message. Determine the first operation event corresponding to the first request message based on any one of the operation object, operation content or operation result of the first request message, or any combination thereof.

3. The method according to claim 1, wherein if the server determines that it has not started executing the first operation event, the method further includes:

Start executing the first operation event, and create a first cached message queue corresponding to the first operation event.

4. The method according to any one of claims 1 to 3, characterized in that the server caches the first request message before the first cached message queue, and further includes:

The server determines whether the first operation event is a preset merge processing event, and if so, performs the step of caching the first request message in the first cache message queue; if not, the server The first request message initiates execution of the first operation event.

5. The method according to claim 4, wherein the preset merge processing events include: operation processing events that increase server CPU processing time and efficiency.

6. The method according to claim 5, characterized in that the operation processing events that increase the server CPU processing time and efficiency include at least one of the following operation events: Add operations, create operations, delete operations, modify operations, query operations, restart operations, backup operations, start operations, and stop operations.

7. The method according to any one of claims 1 to 4, wherein the response to the first operation event is sent to all clients corresponding to all request messages in the first cached message queue. After the message, it also includes:

Delete the first cached message queue.

8. A server, characterized by including:

The receiving module is used to receive the first request message sent by the client;

Determining module, configured to determine the first operation event corresponding to the first request message according to the attribute information of the first request message;

The processing module is used to determine whether it has started to execute the first operation event. If it has started to execute the first operation event, cache the first request message in the first cache message queue. The first cache message The queue is used to cache different request messages sent by different clients, and the same first operation event needs to be executed for different request messages sent by different clients in the first cached message queue;

A sending module, configured to send a response message of the first operation event to each client corresponding to different request messages in the first cache message queue when the execution of the first operation event is completed.

9. The server according to claim 8, characterized in that the determination module is specifically configured to determine based on any one of the operation object, operation content or operation result of the first request message, or any combination thereof. The first operation event corresponding to the first request message.

10. The server according to claim 8, wherein the processing module is further configured to start executing the first operation event after determining that it has not started executing the first operation event, and create a corresponding A first cached message queue for the first operation event.

1 1. The server according to any one of claims 8 to 10, further comprising: a preprocessing module, used to determine whether the first operation event is a preset merge processing event, and if so, Then the processing module performs the step of caching the first request message in the first cache message queue; if not, the processing module starts executing the first operation event for the first request message.

12. The server according to claim 11, characterized in that, the preset merging process Events include: Operation processing events that increase server CPU processing time and efficiency.

13. The server according to claim 12, characterized in that the operation processing events that increase the server CPU processing time and efficiency include at least one of the following operation events:

Add operations, create operations, delete operations, modify operations, query operations, restart operations, backup operations, start operations, and stop operations.

14. The server according to any one of claims 8 to 11, further comprising: a deletion module, configured to send in the sending module to all requests corresponding to all request messages in the first cache message queue. After sending the response message of the first operation event, the client deletes the first cached message queue.

15. A server, characterized by including:

Receiver, used to receive the first request message sent by the client;

The processor is configured to determine the first operation event corresponding to the first request message according to the attribute information of the first request message; determine whether it has started to execute the first operation event. If it has started to execute the first operation event, An operation event, cache the first request message in a first cache message queue, the first cache message queue is used to cache different request messages sent by different clients, for different clients in the first cache message queue Different request messages sent by the terminal need to execute the same first operation event;

A sender, configured to send a response message of the first operation event to each client corresponding to different request messages in the first cache message queue when the execution of the first operation event is completed.

16. The server according to claim 15, characterized in that the processor is specifically configured to determine based on any one of the operation object, operation content or operation result of the first request message, or any combination thereof. The first operation event corresponding to the first request message.

17. The server according to claim 15, wherein the processor is further configured to start executing the first operation event after determining that it has not started executing the first operation event, and create a server corresponding to the first operation event. The first cached message queue for the first operation event.

18. The server according to any one of claims 15 to 17, wherein the processor is further configured to determine whether the first operation event is a preset merge processing event, and if so, execute the The step of caching the first request message in the first cached message queue; if not, initiating execution of the first operation event for the first request message.

19. The server according to claim 18, characterized in that: the preset merging location Processing events include: Operation processing events that increase server CPU processing time and efficiency.

20. The server according to claim 19, characterized in that the operation processing events that increase the server CPU processing time and efficiency include at least one of the following operation events:

21. The server according to any one of claims 15 to 18, characterized in that, the processor is further configured to send messages from the sender to all clients corresponding to all request messages in the first cache message queue. After the terminal sends the response message of the first operation event, the first cached message queue is deleted.