WO2020181913A1

WO2020181913A1 - Message distribution processing method, device, equipment, and storage medium

Info

Publication number: WO2020181913A1
Application number: PCT/CN2020/070692
Authority: WO
Inventors: 王岳晨
Original assignee: 北京字节跳动网络技术有限公司
Priority date: 2019-03-13
Filing date: 2020-01-07
Publication date: 2020-09-17
Also published as: CN111694674B; CN111694674A

Abstract

A message distribution processing method, device, equipment and a storage medium. The method comprises: a client receives a target message pushed by a server through a message distributor (S110); the client parses the target message through the message distributor, and generates a distributed message according to the message type and message data in the target message (S120); the client notifies the distributed message to at least one observer object of the message distributor through the message distributor (S130); the client processes the monitored distributed message through the at least one observer object according to a set processing mode (S140).

Description

Message distribution processing method, device, equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 201910189864.5 on March 13, 2019. The entire content of the application is incorporated into this application by reference.

Technical field

The embodiments of the present disclosure relate to computer technology, for example, to a message distribution processing method, device, device, and storage medium.

Background technique

When the application software client is in use, it often receives various messages pushed by the server, so that related objects in the client can process the received messages.

In related technologies, when an application client running on the iOS operating system receives a message pushed by the server, it does not have an effective message distribution processing mechanism, and mainly relies on one or more object processes currently running in the client (for example, interface Or a pop-up window, etc.) respectively analyze and process each received message to determine whether it belongs to the message processed by the target process, and obtain information matching the target process for processing.

The disadvantage of the related technical solutions is that all object processes need to parse and process each message received, which not only takes up a large amount of memory resources, but also reduces the efficiency of message distribution processing.

Summary of the invention

The embodiments of the present disclosure provide a message distribution processing method, device, equipment, and storage medium, so as to save memory resources and improve the efficiency of message distribution processing.

The embodiment of the present disclosure provides a message distribution processing method, including:

The client receives the target message pushed by the server through the message distributor;

The client parses the target message through the message distributor, and generates a distribution message according to the message type and message data in the target message;

The client terminal notifies at least one observer object of the message distributor of the distribution message through the message distributor;

The client uses the at least one observer object to process the monitored distribution message according to a set processing mode.

The embodiment of the present disclosure also provides a message distribution processing device, which is configured in the client, and the device includes:

The message receiving module is set to receive the target message pushed by the server through the message distributor;

A message parsing module, configured to parse the target message through the message distributor, and generate a distribution message according to the message type and message data in the target message;

A message distribution module, configured to notify at least one observer object of the message distributor of the distribution message through the message distributor;

The message processing module is configured to process the monitored distribution message according to the set processing mode through the at least one observer object.

The embodiment of the present disclosure also provides a message distribution processing device, which is configured in a client, and the device includes: a message distributor and at least one observer object;

The message distributor is set to receive the target message pushed by the server; parse the target message, and generate a distribution message according to the message type and message data in the target message; notify the message of the distribution message At least one observer object of the dispatcher;

The at least one observer object is set to process the monitored distribution message according to a set processing mode.

The embodiment of the present disclosure also provides a terminal device, which includes:

One or more processing devices;

Storage device, set to store one or more programs;

When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the message distribution processing method according to any one of the embodiments of the present disclosure.

The embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processing device, the method for message distribution processing as described in any of the embodiments of the present disclosure is implemented.

Description of the drawings

FIG. 1 is a schematic flowchart of a message distribution processing method provided by Embodiment 1 of the present disclosure;

2 is a schematic flowchart of a message distribution processing method provided by Embodiment 2 of the present disclosure;

FIG. 3 is a schematic structural diagram of a message distribution processing apparatus provided by Embodiment 3 of the present disclosure;

FIG. 4 is a schematic diagram of the hardware structure of a terminal device provided in the fourth embodiment of the present disclosure.

detailed description

The present disclosure will be described below with reference to the drawings and embodiments. The specific embodiments described here are only used to explain the present disclosure, but not to limit the present disclosure. For ease of description, only a part of the structure related to the present disclosure is shown in the accompanying drawings instead of all of the structure.

In the following embodiments, each embodiment provides optional features and examples at the same time. Multiple features recorded in the embodiments can be combined to form multiple alternative solutions. Each numbered embodiment should not be regarded as It is a technical solution.

Example one

FIG. 1 is a schematic flowchart of a message distribution processing method according to Embodiment 1 of the present disclosure. This method can be applied to the case where the client distributes the received message. The method can be executed by a terminal device such as a mobile phone or a tablet computer running an application client, and includes the following steps:

S110. The client receives the target message pushed by the server through the message distributor.

In this embodiment, the target message may be personal information such as private messages and notifications pushed by the server to the client. Since the iOS operating system in related technologies does not have an effective message distribution processing mechanism, when the client receives the target message pushed by the server, it can only rely on all the objects (also called processes or instances, etc.) in the client. Analyze each received message to determine whether the object is the processor of the message, so that each object needs to perform a repeated analysis process for each message. When a large number of push messages are received at the same time, it will cause customers The client occupies a large amount of memory resources, which makes the operation of the client stalled, and at the same time, it reduces the efficiency of message distribution processing.

In order to solve the above-mentioned problem, in this embodiment, a message dispatcher (MessageDispatcher) is set in the client, which is specifically used to parse and distribute received push messages. Among them, the message distributor can be a processing thread written in the client program. When the server pushes the target message to the client, the client can receive the target message through the message distributor.

The client involved in this embodiment may refer to a mobile application (Application, APP) or a web page, which is not limited here.

Optionally, the client includes: an application client adapted to the iOS operating system. That is, the client involved in this embodiment can be installed in the iOS operating system to make up for the lack of an effective message distribution processing mechanism in the iOS operating system. Of course, the client can also be adapted to the Android operating system. The application client, etc., this embodiment does not limit this.

S120. The client parses the target message through the message distributor, and generates a distribution message according to the message type and message data in the target message.

In this embodiment, after receiving the target message pushed by the server, the client can use the message distributor to uniformly analyze the target message. In an embodiment, the client can split or recognize the target message into message data and its corresponding message type through the message distributor.

Exemplarily, the parsed message data and message type can be generated according to a preset format to generate a distribution message. For example, the preset format can be "message type + message data" so that the message can be processed directly in the subsequent steps. Identify the distribution message according to the message type.

S130. The client informs at least one observer object of the message distributor of the distribution message through the message distributor.

In this embodiment, the observer object may be an object in the client that needs to receive distribution messages, and the object includes, but is not limited to, a web page, a pop-up window, etc. in the client. Exemplarily, after the client generates a distribution message through the message distributor, it can notify each observer object of the message distributor of the distribution message, so that the observer object can process the pushed message. In an embodiment, a listener thread may be set for each observer object to listen to the distribution message generated in the message distributor.

In an optional implementation manner, the client terminal notifies at least one observer object of the message distributor of the distribution message through the message distributor, including: the client terminal notifies the distribution message to the message type according to the message type through the message distributor. At least one observer object of the matched message distributor.

Since the types of messages that can be processed by different observer objects may not be the same, the message distributor can notify the corresponding observer object capable of processing the message type according to the message type, so that the corresponding observer object pairs The monitored distribution message is processed directly. In an embodiment, the corresponding relationship between the message type and the observer object can be preset, and the message distributor can determine to notify the corresponding observer object of the distribution messages of different message types through the corresponding relationship.

In another optional implementation manner, the client notifies at least one observer object of the message distributor of the distribution message through the message distributor, including: the client notifies the distribution message in the message distributor in advance through the message distributor. At least one observer object registered.

When at least one object in the client needs to receive a message pushed by the server, it can be registered in the message distributor in advance. For a practical example, if the user's opening operation for the target webpage in the client is detected, the target webpage can be automatically registered in the message distributor as an observer object. Similarly, if the user's opening operation for the target pop-up window in the client is detected, the target pop-up window can also be automatically registered in the message distributor as another observer object.

Since the objects in the client that are interested in the messages pushed by the server are registered in the message distributor in advance, when the message distributor generates a distribution message, only the registered observer object can receive the distribution message notification, which can avoid all All objects listen to messages indiscriminately, reducing the waste of memory resources and improving the performance of the device where the client is located.

S140: The client uses at least one observer object to process the monitored distribution message according to a set processing mode.

Since the messages that can be processed by different objects in the client may be different, and the distribution messages monitored by the observer object may only include messages that can be processed by itself, or may also include other messages. In this case, you can follow the set processing method to Distribute messages for processing.

Exemplarily, when the observer object listens to the distribution message, it can display or respond to the message that it can handle, and discard the message that cannot be processed.

In the above step S130, in the first optional implementation manner, correspondingly, the client uses at least one observer object to process the monitored distribution message according to the set processing mode, including: the client uses at least one observer The object processes the distribution messages that it monitors.

In this case, because the distribution message monitored by the observer object is a message notified by the message distributor according to the message type, the distribution message monitored by the observer object only includes the messages that it can process, and only the distribution message is required Perform the corresponding message processing.

In the above step S130, in the second optional implementation manner, correspondingly, the client uses at least one observer object to process the monitored distribution message according to the set processing mode, including: the client uses at least one observer The object determines the processing mode of the distribution message according to the message type in the monitored distribution message, and processes the distribution message according to the processing mode.

Since the distribution message monitored by the observer object is the distribution message for the indiscriminate notification of the message distributor, when the observer object monitors the distribution message generated by the message distributor through the monitoring thread, it can be based on the message type included in the distribution message, Different processing methods are adopted for distributed messages.

For example, when the observer object is a pop-up window, the message type it can process can be the notification type; when the observer object is a web page, the message type it can process can be the private message type, and so on. Exemplarily, the processing method for the distribution message includes but is not limited to discarding, displaying, responding, etc., which are not limited herein, wherein the processing method for the distribution message can be determined according to the message type in the distribution message.

Optionally, the client determines the processing mode of the distribution message according to the message type in the monitored distribution message through at least one observer object, and processing the distribution message according to the processing mode includes: the client verifies the at least one observer object Whether the message type of the monitored distribution message is the preset target monitoring type; when the message type of the distribution message is the preset target monitoring type, the message data in the monitored distribution message is processed, and the If the message type of the message is not the preset target monitoring type, the distribution message that is monitored is discarded.

In this embodiment, since the types of messages that can be processed by different objects may be different, different observer objects can correspondingly set different target listening types. In addition, the message types that can be processed by an observer object can include one or more types, and correspondingly, the target monitoring types also include one or more types.

Exemplarily, when the observer object determines that the message type of the monitored distribution message is the preset target monitoring type corresponding to it, it means that the observer object is the processor of the distribution message, and the distribution message can be When the observer object determines that the message type of the monitored distribution message does not belong to the corresponding preset target monitoring type, it means that the observer object is not the processor of the distribution message. Discard the monitored distribution message directly.

In the technical solution of this embodiment, by setting a message distributor in the client, the message distributor is used to receive the target message pushed by the server, and the target message is parsed, and the distribution message is generated according to the message type and message data in the target message , And then notify the distribution message to at least one observer object in the message distributor, and process the monitored distribution message according to the set processing method through the at least one observer object, and use the separate message distributor to complete the process. The message parsing and distribution process solves the problems of related technologies that all objects in the client need to parse each message received, which causes a large amount of memory, reduces the efficiency of message distribution and processing, and saves memory resources. Improve the efficiency of message distribution processing.

On the basis of the foregoing embodiment, optionally, the message distributor exposes the protocol method to the outside; at least one observer object completes the monitoring of the message notified by the message distributor by implementing the protocol method exposed by the message distributor.

Exemplarily, an externally exposed protocol method can be pre-defined in the message distributor as an interface for the message distributor to publish and distribute message notifications, and the observer object can implement the protocol method by calling to monitor the interface. Wherein, the protocol method may be a global method, including parameters used to carry the distribution message.

Example two

FIG. 2 is a schematic flowchart of a message distribution processing method provided by Embodiment 2 of the disclosure. This embodiment is described on the basis of the optional solutions in the above embodiments, and provides an optional message distribution processing method. Before the client receives the target message pushed by the server through the message distributor, it also includes: the client sends the message according to the server Establish a long connection between the target domain name and the server. The client receives the target message pushed by the server through the message distributor, including: the client receives the target message pushed by the server through the message distributor using a long connection.

The message distribution processing method provided in this embodiment includes the following steps:

S210. The client establishes a persistent connection with the server according to the target domain name issued by the server.

In this embodiment, a long connection means that multiple data packets can be sent continuously on one connection. During the connection maintenance period, if no data packets are sent, both parties need to send link detection packets. Long connections are mostly used for frequent operations, point-to-point communication, and the number of connections cannot be too many. Since each Transmission Control Protocol (TCP) connection requires a three-way handshake, which requires a lot of time, if each operation is a short connection, the processing speed will be greatly reduced, so after each operation is completed On, the data packet can be sent directly during the next processing without re-establishing the TCP connection.

In this embodiment, since the server continuously pushes messages to the client during the use of the client, a long connection can be established between the client and the server, so as to save communication time and increase the message transmission speed. In one embodiment, the server may be correspondingly set with multiple domain names, and when the server delivers the domain name to the client, it can select the most suitable target domain name for the client, so that the client establishes a persistent connection with the server according to the target domain name.

Compared with the manner in which a fixed domain name is configured for each client for server connection in related technologies, the beneficial effect of adopting a dynamic domain name for server connection in this embodiment is that the optimal data transmission path can be selected at any time according to changes in the location of the client, which improves Message push efficiency.

Optionally, before the client establishes a persistent connection with the server according to the target domain name issued by the server, it also includes: the client sends a domain name request to the server when detecting the client start instruction; the domain name request is used to instruct the server to use the preset The speed measurement algorithm of the server determines the target domain name matching the client from at least two candidate domain names corresponding to the server, and delivers the target domain name to the client.

Exemplarily, if the server in this embodiment is a server cluster, including multiple server rooms, and the server rooms are located in different locations, and one server room corresponds to a domain name, in order to improve the access speed, the server can choose the best for the client. Suitable server room for connection. When the client is started, the client start command can be detected. At this time, it can send a domain name request to the server. After the server receives the domain name request, it can select the client from multiple server rooms according to the preset speed measurement algorithm The server room with the fastest access speed is used as the server to be connected to the client, and the domain name corresponding to the server room is issued to the client as the target domain name, so that the client establishes a connection with the server according to the target domain name.

In an optional implementation of this embodiment, the preset speed measurement algorithm may be that the domain names corresponding to several server rooms that are close to the client are used as candidate domain names, and the client sends the candidate domain names to the candidate domain names respectively. When sending speed measurement data packets, the server determines the speed of each link according to the receiving and sending time, and then selects the fastest candidate domain name as the target domain name and sends it to the client.

In an embodiment, in another optional implementation manner, the preset speed measurement algorithm may be to use the domain names corresponding to several server rooms close to the client as candidate domain names, and calculate each candidate The number of router nodes in the link corresponding to the domain name, so that the candidate domain name with the least number of router nodes passed is delivered to the client as the target domain name.

S220: The client receives the target message pushed by the server through a long connection through the message distributor.

Exemplarily, when the client obtains the target domain name issued by the server, it can establish a long connection with the server according to the target domain name, and use the long connection link to receive the target message pushed by the server, which improves the message push efficiency.

S230. The client parses the target message through the message distributor, and generates a distribution message according to the message type and message data in the target message.

S240. The client informs at least one observer object pre-registered in the message distributor of the distribution message through the message distributor.

S250: The client determines a processing method for the distribution message according to the message type in the monitored distribution message through at least one observer object.

The technical solution of this embodiment establishes a persistent connection with the server according to the issued target domain name, and uses the persistent connection to receive the target message pushed by the server. After that, the message distributor is used to parse the target message, according to the message in the target message Type and message data to generate a distribution message, and then notify the distribution message to at least one observer object pre-registered in the message atmosphere. Finally, at least one observer object determines the processing of the distribution message according to the message type in the monitored distribution message In this way, the server is used to dynamically issue the target domain name for the client, and the message pushed by the server is received in a long connection mode, which improves the efficiency of message push, thereby shortening the time of message distribution processing, and improving the efficiency of message distribution processing.

On the basis of the foregoing embodiment, optionally, it further includes: in the case that the client detects an object destruction instruction matching the target observer object, in the message distributor, destroy the registered target observer object .

Exemplarily, when the target observer object exits, such as when the user closes the target webpage, it means that the target observer object no longer needs to receive the message pushed by the server. At this time, it can be determined that an object destruction instruction matching the target observer object is detected . In order to save memory space and release memory resources, when an object destruction instruction matching the target observer object is detected, the registered target observer object in the message distributor can be removed and destroyed.

Example three

FIG. 3 is a schematic structural diagram of a message distribution processing apparatus provided in Embodiment 3 of the disclosure. The message distribution processing device provided in this embodiment can be configured in the client. Referring to FIG. 3, the message distribution processing device includes: a message receiving module 310, a message parsing module 320, a message distribution module 330, and a message processing module 340. Each module is explained.

The message receiving module 310 is configured to receive the target message pushed by the server through the message distributor; the message parsing module 320 is configured to parse and process the target message through the message distributor, and according to the message type and message in the target message The data generates a distribution message; the message distribution module 330 is configured to notify the distribution message to at least one observer object of the message distributor through the message distributor; the message processing module 340 is configured to pass at least one observer object according to the design Processing the monitored distribution message in a predetermined processing manner.

The message distribution processing apparatus provided in this embodiment uses the message distributor to receive the target message pushed by the server by setting the message distributor in the client, and parses the target message according to the message type and message data in the target message Generate a distribution message, and then notify the distribution message to at least one observer object in the message distributor, and process the monitored distribution message according to the set processing method through the at least one observer object, and use the separately set message distribution The server completes the message parsing and distribution process in a unified manner, which solves the problem that all objects in the client need to parse each message received, which causes a large amount of memory and reduces the efficiency of message distribution processing, saving Memory resources improve the efficiency of message distribution processing.

Optionally, the message distribution module 330 is configured to notify at least one observer object of the message distributor that matches the message type of the distribution message according to the message type through the message distributor; Correspondingly, the message processing module 340 is configured to process the monitored distribution message through at least one observer object.

Optionally, the message distribution module 330 is configured to notify at least one observer object pre-registered in the message distributor of the distribution message through the message distributor; correspondingly, the message processing module 340 is configured to The steps are: determining a processing mode for the distribution message according to the message type in the distribution message monitored by at least one observer object, and processing the distribution message according to the processing mode.

Optionally, the device may further include: a link establishment module configured to establish a persistent connection with the server according to the target domain name issued by the server before receiving the target message pushed by the server through the message distributor; the message receiving module 310 is set It is: receiving the target message pushed by the server through the message distributor using the long connection.

Optionally, the device may further include: a request sending module, configured to send the domain name to the server when the client start instruction is detected before establishing a long connection with the server according to the target domain name issued by the server Request; the domain name request is used to instruct the server to use a preset speed measurement algorithm, determine a target domain name matching the client in at least two candidate domain names corresponding to the server, and combine the target domain name Deliver to the client.

Optionally, the message distributor exposes the protocol method to the outside in advance; the at least one observer object completes the monitoring of the message notified by the message distributor by implementing the protocol method exposed by the message distributor.

Optionally, the mode determining module 340 is configured to verify whether the message type of the distribution message monitored is a preset target monitoring type through at least one observer object; when the message type of the distribution message is the In the case of the preset target monitoring type, the message data in the monitored distribution message is processed, and if the message type of the distribution message is not the preset target monitoring type, the monitoring is discarded Of the distribution message.

Optionally, the device may further include: a target destruction module, configured to: in the message distributor, when the client detects an object destruction instruction matching the target observer object, the registered all The target observer object is destroyed.

Optionally, the client includes: an application client adapted to the iOS operating system.

The above-mentioned product can execute the method provided by any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.

The third embodiment of the present disclosure also provides a message distribution processing device, which is configured in the client and includes: a message distributor and at least one observer object; the message distributor is set to receive the target message pushed by the server; The target message is parsed and processed, and a distribution message is generated according to the message type and message data in the target message; the distribution message is notified to at least one observer object of the message distributor; the at least one observer object is set To process the monitored distribution message according to the set processing mode.

Example four

Referring now to FIG. 4, FIG. 4 shows a schematic structural diagram of a terminal device 400 suitable for implementing embodiments of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (Personal Digital Assistant, PDA), tablet computers (PAD), and portable multimedia players (Portable Media Player). , PMP), mobile terminals such as in-vehicle terminals (for example, in-vehicle navigation terminals), and fixed terminals such as digital televisions (Television, TV), desktop computers, etc. The terminal device shown in FIG. 4 is only an example, and should not bring any limitation to the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 4, the terminal device 400 may include a processing device (such as a central processing unit, a graphics processor, etc.) 401, which may be based on a program stored in a read-only memory (Read-Only Memory, ROM) 402 or from a storage device 408 A program loaded into a random access memory (Random Access Memory, RAM) 403 executes various appropriate actions and processes. In the RAM 403, various programs and data required for the operation of the terminal device 400 are also stored. The processing device 401, ROM 402, and RAM 403 are connected to each other through a bus 404. An input/output (Input/Output, I/O) interface 405 is also connected to the bus 404.

Generally, the following devices can be connected to the I/O interface 405: including input devices 406 such as touch screen, touch panel, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD) , Output devices 407 such as speakers, vibrators, etc.; storage devices 408 such as magnetic tapes, hard disks, etc.; and communication devices 409. The communication device 409 may allow the terminal device 400 to perform wireless or wired communication with other devices to exchange data. Although FIG. 4 shows a terminal device 400 having multiple devices, it is not required to implement or have all the illustrated devices. It may alternatively be implemented or provided with more or fewer devices.

According to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer software program. For example, the embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device 409, or installed from the storage device 408, or installed from the ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

The aforementioned computer-readable medium in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. Examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, RAM, ROM, Erasable Programmable Read-Only Memory (EPROM) Or flash memory), optical fiber, CD-ROM (Compact Disc Read-Only Memory), optical storage device, magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium. The computer-readable signal medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device . The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.

The above-mentioned computer-readable medium may be included in the above-mentioned terminal device; or it may exist alone without being assembled into the terminal device.

The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the terminal device, the client in the terminal device: receives the target message pushed by the server through the message distributor; The message distributor parses the target message, and generates a distribution message according to the message type and message data in the target message; at least one of the message distributors is notified of the distribution message through the message distributor Observer object; the at least one observer object is used to process the monitored distribution message according to a set processing mode.

The computer program code used to perform the operations of the present disclosure may be written in one or more programming languages or a combination thereof. The above-mentioned programming languages include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional Procedural programming language-such as "C" language or similar programming language. The program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any kind of network-including Local Area Network (LAN) or Wide Area Network (WAN)-or it can be connected to an external computer ( For example, use an Internet service provider to connect via the Internet).

The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation of the system architecture, functions, and operations of the system, method, and computer program product according to the embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram can represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logical function Executable instructions. It should also be noted that, in some alternative implementations, the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.

The modules or units involved in the described embodiments of the present disclosure can be implemented in software or hardware. Among them, the name of the module or unit does not constitute a limitation on the module or unit itself in one case. For example, the message receiving module can also be described as "a module for receiving target messages pushed by the server through a message distributor" .

Claims

A message distribution processing method, including:

The client receives the target message pushed by the server through the message distributor;

The client parses the target message through the message distributor, and generates a distribution message according to the message type and message data in the target message;

The client terminal notifies at least one observer object of the message distributor of the distribution message through the message distributor;

The client uses the at least one observer object to process the monitored distribution message according to a set processing mode.
The method according to claim 1, wherein the client notifying the distribution message to at least one observer object of the message distributor through the message distributor comprises:

The client, through the message distributor, notifies at least one observer object of the message distributor matching the message type of the distribution message according to the message type;

The client processing the monitored distribution message according to the set processing mode through the at least one observer object includes:

The client uses the at least one observer object to process the monitored distribution message.
The method according to claim 1, wherein the client notifying the distribution message to at least one observer object of the message distributor through the message distributor comprises:

The client informs at least one observer object pre-registered in the message distributor of the distribution message through the message distributor;

The client processing the monitored distribution message according to the set processing mode through the at least one observer object includes:

The client determines a processing mode for the distribution message according to the monitored message type in the distribution message through the at least one observer object, and processes the distribution message according to the processing mode.
The method according to claim 1, before the client receives the target message pushed by the server through the message distributor, further comprising:

The client establishes a persistent connection with the server according to the target domain name issued by the server;

The client receiving the target message pushed by the server through the message distributor includes:

The client receives the target message pushed by the server through the message distributor using the long connection.
The method according to claim 4, before the client establishes a persistent connection with the server according to the target domain name issued by the server, further comprising:

The client sends a domain name request to the server when the client start instruction is detected;

The domain name request is used to instruct the server to adopt a preset speed measurement algorithm, determine a target domain name matching the client from at least two candidate domain names corresponding to the server, and deliver the target domain name To the client.
The method according to any one of claims 1-5, further comprising:

The client terminal exposes the protocol method to the outside in advance through the message distributor;

The client implements the protocol method exposed by the message distributor through the at least one observer object to complete the monitoring of the message notified by the message distributor.
The method according to claim 3, wherein the client determines the processing mode for the distribution message according to the message type in the distribution message monitored by the at least one observer object, and according to the processing Ways to process the distribution message include:

The client verifies whether the message type of the distribution message monitored by the at least one observer object is a preset target monitoring type;

In the case that the message type of the distribution message is the preset target monitoring type, processing the message data in the monitored distribution message;

In the case that the message type of the distribution message is not the preset target monitoring type, discard the monitored distribution message.
The method according to any one of claims 1-5, further comprising:

In the case that the client detects an object destruction instruction that matches the target observer object, in the message distributor, the registered target observer object is destroyed.
A message distribution processing device, configured in a client, includes:

The message receiving module is set to receive the target message pushed by the server through the message distributor;

A message parsing module, configured to parse the target message through the message distributor, and generate a distribution message according to the message type and message data in the target message;

A message distribution module, configured to notify at least one observer object of the message distributor of the distribution message through the message distributor;

The message processing module is configured to process the monitored distribution message according to the set processing mode through the at least one observer object.
A message distribution processing device, configured in a client, includes: a message distributor and at least one observer object;

The message distributor is set to receive the target message pushed by the server; parse the target message, and generate a distribution message according to the message type and message data in the target message; notify the message of the distribution message At least one observer object of the dispatcher;

The at least one observer object is set to process the monitored distribution message according to a set processing mode.
A terminal device, including:

One or more processing devices;

Storage device, set to store one or more programs;

When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the message distribution processing method according to any one of claims 1-8.
A computer-readable storage medium storing a computer program, which when executed by a processing device, realizes the message distribution processing method according to any one of claims 1-8.