[go: up one dir, main page]

WO2014078989A1 - Procédé de traitement de messages, et serveur - Google Patents

Procédé de traitement de messages, et serveur Download PDF

Info

Publication number
WO2014078989A1
WO2014078989A1 PCT/CN2012/084897 CN2012084897W WO2014078989A1 WO 2014078989 A1 WO2014078989 A1 WO 2014078989A1 CN 2012084897 W CN2012084897 W CN 2012084897W WO 2014078989 A1 WO2014078989 A1 WO 2014078989A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
message
operation event
request message
event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2012/084897
Other languages
English (en)
Chinese (zh)
Inventor
李亿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2012/084897 priority Critical patent/WO2014078989A1/fr
Priority to CN201280003447.3A priority patent/CN103370917B/zh
Publication of WO2014078989A1 publication Critical patent/WO2014078989A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • 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.
  • 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.
  • 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.
  • 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
  • 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;
  • 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.
  • the method further includes:
  • 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.
  • the preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency.
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • the preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency.
  • the adding The operation processing event of the 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the preset merge processing event includes, but is not limited to, an operation processing event that increases server CPU processing time and efficiency.
  • 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.
  • 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 for executing instructions stored in a memory
  • a communication interface for storing data
  • a memory for storing instructions
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Embodiment 1 is a flowchart of Embodiment 1 of a message processing method according to the present invention
  • Embodiment 2 is a flowchart of Embodiment 2 of a message processing method according to the present invention
  • Embodiment 1 of a server according to the present invention is a schematic structural diagram of Embodiment 1 of a server according to the present invention.
  • Embodiment 2 of a server according to the present invention 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.
  • FIG. 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:
  • the server receives a first request message sent by the client.
  • 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.
  • the first request message is a request message of any event that can be processed by the client requesting the server.
  • the server determines, according to the attribute information of the first request message, a first operation event corresponding to the first request message.
  • 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.
  • the operation object included in the first request message is a server information list
  • the operation content is a query
  • 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”.
  • the server determines whether it has started to execute the first operation event.
  • 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.
  • 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.
  • the server puts the first request message into the first cache message queue and waits for the first operation event requested by the server.
  • 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.
  • the server 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operational 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.
  • the first operation event is a preset merge processing event
  • the first request message is cached in the first cache message queue
  • the server may start for the first request message. Execute the first operational event.
  • the "query A server” event is a preset merge processing event
  • the "query current user number” event is a preset non-merging processing event
  • the server learns the request message according to the attribute information of the received request message.
  • 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.
  • the method further includes: deleting 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.
  • FIG. 2 is a flowchart of a second embodiment of a message processing method according to the present invention.
  • FIG. 2 is processed by a Hypertext Transfer Protocol (http) server.
  • http Hypertext Transfer Protocol
  • the message interaction module of the http server receives the request message sent by the http client, and the http client may be multiple.
  • 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.
  • the request message is placed.
  • 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.
  • 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.
  • the message processing module processes the query operation name for the query name name http://10.122.101.43 :8080/hwm/server.
  • 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.
  • 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.
  • 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.
  • the message interaction module returns the above response message to all of the above 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 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.
  • Tcp/udp Transmission Control Protocol/User Datagram Protocol
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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:
  • processor Rocessor
  • communication interface 520 a communication interface 520
  • memory 530 a memory 530
  • bus 540 a bus 540
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 .
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé de traitement de messages, et un serveur. Le procédé de traitement de messages selon l'invention comprend : la réception, par le serveur, d'un premier message de demande transmis par un client; sur la base d'informations de propriété du premier message de demande, la détermination d'un premier événement opérationnel correspondant au premier message de demande; si le serveur a commencé à exécuter le premier événement opérationnel, la mise en cache du premier message de demande dans une première file d'attente de messages mis en cache, la première file d'attente de messages mis en cache étant utilisée pour mettre en cache différents messages de demande transmis par différents clients, et le serveur devant exécuter le même premier événement opérationnel pour les différents messages de demande transmis par différents clients dans la première file d'attente de messages mis en cache; enfin, quand le serveur a fini d'exécuter le premier événement opérationnel, la transmission, par le serveur, d'un message de réponse du premier événement opérationnel à chaque client correspondant aux différents messages de demande dans la première file d'attente de messages mis en cache. Le procédé selon l'invention réduit ainsi le surdébit nécessaire au serveur pour traiter le même événement opérationnel, et améliore l'efficacité de traitement du serveur.
PCT/CN2012/084897 2012-11-20 2012-11-20 Procédé de traitement de messages, et serveur Ceased WO2014078989A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2012/084897 WO2014078989A1 (fr) 2012-11-20 2012-11-20 Procédé de traitement de messages, et serveur
CN201280003447.3A CN103370917B (zh) 2012-11-20 2012-11-20 消息处理方法及服务器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/084897 WO2014078989A1 (fr) 2012-11-20 2012-11-20 Procédé de traitement de messages, et serveur

Publications (1)

Publication Number Publication Date
WO2014078989A1 true WO2014078989A1 (fr) 2014-05-30

Family

ID=49370150

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/084897 Ceased WO2014078989A1 (fr) 2012-11-20 2012-11-20 Procédé de traitement de messages, et serveur

Country Status (2)

Country Link
CN (1) CN103370917B (fr)
WO (1) WO2014078989A1 (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103677844B (zh) * 2013-12-20 2017-02-01 国云科技股份有限公司 一种基于消息链的轻量级数据处理方法
CN105656853B (zh) * 2014-11-14 2018-11-20 华为技术有限公司 一种消息传递方法及相关装置
CN104618517B (zh) * 2015-03-05 2018-08-07 国家电网公司 一种推送消息的方法、系统及装置
CN104683731B (zh) * 2015-03-20 2019-02-19 苏州科达科技股份有限公司 一种用于异构平台间通信的方法及系统
CN105049240B (zh) * 2015-06-26 2018-08-21 大唐移动通信设备有限公司 一种消息处理方法及服务器
CN108694075B (zh) * 2017-04-12 2021-03-30 北京京东尚科信息技术有限公司 处理报表数据的方法、装置、电子设备和可读存储介质
CN110020271A (zh) * 2017-08-04 2019-07-16 北京京东尚科信息技术有限公司 用于缓存管理的方法和系统
CN107592556B (zh) * 2017-08-08 2020-02-04 福建星网视易信息系统有限公司 基于移动终端的控制信息合成方法及受控终端和移动终端
CN110505257A (zh) * 2018-05-17 2019-11-26 北京国双科技有限公司 请求消息处理方法及装置
CN111753164B (zh) * 2019-03-27 2025-04-15 北京京东尚科信息技术有限公司 链路事件引导方法、装置、电子设备及存储介质
CN111917617B (zh) * 2020-07-31 2022-03-29 宁波奥克斯电气股份有限公司 智能家电设备控制方法、装置、服务器及存储介质
CN112199215B (zh) * 2020-10-13 2024-01-19 恒生电子股份有限公司 消息处理方法、装置、设备及存储介质
CN114598894B (zh) * 2020-12-03 2024-12-10 北京字节跳动网络技术有限公司 交互消息处理方法、装置、设备和介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008085324A1 (fr) * 2006-12-19 2008-07-17 Ianywhere Solutions, Inc. Attribution de tâches à des fils nécessitant des ressources limitées à l'aide de files d'attente programmables
CN101447981A (zh) * 2008-04-03 2009-06-03 中兴通讯股份有限公司 基于ldap协议的客户端与服务器的交互方法及系统
CN101998682A (zh) * 2009-08-27 2011-03-30 中兴通讯股份有限公司 一种个人网设备获取业务内容的装置、方法及相关装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2044428A2 (fr) * 2006-07-14 2009-04-08 ExxonMobil Research and Engineering Company Expérimentation rapide en série de catalyseurs et systems de catalyseurs
CN101639792B (zh) * 2008-07-29 2016-04-06 阿里巴巴集团控股有限公司 一种并发数据处理方法、装置及一种电子记账系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008085324A1 (fr) * 2006-12-19 2008-07-17 Ianywhere Solutions, Inc. Attribution de tâches à des fils nécessitant des ressources limitées à l'aide de files d'attente programmables
CN101447981A (zh) * 2008-04-03 2009-06-03 中兴通讯股份有限公司 基于ldap协议的客户端与服务器的交互方法及系统
CN101998682A (zh) * 2009-08-27 2011-03-30 中兴通讯股份有限公司 一种个人网设备获取业务内容的装置、方法及相关装置

Also Published As

Publication number Publication date
CN103370917A (zh) 2013-10-23
CN103370917B (zh) 2016-03-02

Similar Documents

Publication Publication Date Title
WO2014078989A1 (fr) Procédé de traitement de messages, et serveur
CN102984286B (zh) 一种dns服务器的缓存更新方法、装置及系统
CN103024053B (zh) 云存储方法、资源调度系统、云存储节点及系统
CN106453667B (zh) 更新缓存数据的方法及装置
WO2017114205A1 (fr) Procédé de traitement de lien court, dispositif et serveur
WO2016023357A1 (fr) Procédé et appareil d'accès à une page web et routeur
JP2017529793A5 (fr)
WO2014044103A1 (fr) Procédé et appareil de mise en mémoire cache en différé
WO2015067117A1 (fr) Procédé et système de téléchargement vers le nuage, dispositif de planification et client
US20180013610A1 (en) File delivery method, apparatus and system
WO2014179950A1 (fr) Procédé, client et serveur de téléchargement amont de fichiers
CN113961832B (zh) 页面渲染的方法、装置、设备、存储介质及程序产品
WO2019006775A1 (fr) Procédé de transmission de données et système associé
WO2017185633A1 (fr) Serveur de cdn et son procédé de placement en antémémoire de données
WO2014205842A1 (fr) Procédé de partage de contenu et appareil de synchronisation sociale
US9967360B2 (en) Method and system for information exchange utilizing an asynchronous persistent store protocol
US9832268B2 (en) System, method, and medium for managing priority in requests to in-memory data grid (IMDG)
CN102984138B (zh) 一种获取对象的方法、装置和系统
WO2013104181A1 (fr) Procédé et dispositif de gestion de ressources
CN103957252B (zh) 云储存系统的日志获取方法及其系统
CN114301872B (zh) 基于域名的访问方法及装置、电子设备、存储介质
WO2017136979A1 (fr) Procédé d'implémentation, appareil et système destinés à l'accès à distance
WO2011120450A2 (fr) Procédé d'acquisition de contenu, et client à base de http
WO2010031297A1 (fr) Procédé et système de service d’extraction d’une passerelle wap
US11012537B2 (en) Method for handling long-running client-server processes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12888675

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12888675

Country of ref document: EP

Kind code of ref document: A1