CA3131954C - Information synchronization method, system, apparatus, computer device and storage medium - Google Patents
Information synchronization method, system, apparatus, computer device and storage medium Download PDFInfo
- Publication number
- CA3131954C CA3131954C CA3131954A CA3131954A CA3131954C CA 3131954 C CA3131954 C CA 3131954C CA 3131954 A CA3131954 A CA 3131954A CA 3131954 A CA3131954 A CA 3131954A CA 3131954 C CA3131954 C CA 3131954C
- Authority
- CA
- Canada
- Prior art keywords
- message
- clients
- long connection
- topic
- messages
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000004590 computer program Methods 0.000 claims description 34
- 230000007246 mechanism Effects 0.000 claims description 14
- 238000013507 mapping Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 claims description 6
- 238000012423 maintenance Methods 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 26
- 238000010586 diagram Methods 0.000 description 14
- OUADMZZEIRSDSG-NKFUZKMXSA-N C1N2C(C(C(C)=C(N)C3=O)=O)=C3[C@@H](CO)[C@@]2(OC)[C@@H]2[C@H]1N2 Chemical compound C1N2C(C(C(C)=C(N)C3=O)=O)=C3[C@@H](CO)[C@@]2(OC)[C@@H]2[C@H]1N2 OUADMZZEIRSDSG-NKFUZKMXSA-N 0.000 description 7
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
AND STORAGE MEDIUM
Field [0001] The present disclosure relates to the field of information processing technology and particularly to an information synchronization method, system, apparatus, computer device and storage medium.
Background
are requested respectively, the back-end server A is requested to maintain the message topics from a plurality of clients. The client 1 and client 2 send the messages to the same back-end server. The back-end server A is requested to maintain all the clients' connections associated with the topic.
For example, the client 1 sends the message which needs to be forwarded to client 2, client 2 send the message which needs to be forwarded to client 1. When there are a plurality of clients, single back-end server A will be overwhelmed. If there is another message topic needs to be synchronized, the maintenance of a plurality of clients from back-end server A will become very complicated and difficult.
Invention Content
receiving the messages and message topics sent by the clients, publishing the messages and the message topics to the message middleware, so that any server subscribes the messages and the message topics from the message middleware; Subscribing the topic messages associated with the message topics in the message middleware, the message middleware is used to receive the topic messages published by any server; In one of the implementations, the method also includes: establishing a long connection with the clients, generating the clients' identities of the clients;
associating the long connection with the clients' identities; receiving the messages and message topics sent by the clients, including: receiving the messages and the message topics sent by the clients through the long connection; pushing the topic messages to the clients synchronously, including: determining the long connection according to the clients' identities, publishing the topic messages to the clients synchronously through the long connection.
associating the long connection with the clients' identities, including:
establishing the first long connection with the first client, establishing the second long connection with the second client; generating the first identity of the first client, and generating the second identity of the second client;
and the first long connection is associated with the first identity, the second long connection is associated with the second identity; the messages and the message topics sent by the clients are received through the long connection, including:
receiving the messages and the message topics sent by the first client through the first long connection, and receiving the messages and the message topics sent by the second client through the second long connection;
determining the long connection according to the clients' identities, and pushing the topic messages to the clients synchronously through the long connection, including: determining the first long connection according to the first identity, pushing the topic message synchronously to the first client through the first long connection; determining the second the long connection according to the second identity, pushing the topic message synchronously to the second client through the second long connection.
Date Recue/Date Received 2021-09-27
Which concludes that the server pushes the clients' message topics and subscribes the topic messages related to the message topics through the message middleware, and achieving the information synchronization of the message topics by forwarding the topic messages associated with the same message topics without using a single server, when maintaining a plurality of the message topics, the server capacity can be quicky expanded by controlling a plurality of clients to connect to different servers. Meanwhile, there is no need to achieve the information synchronization and forwarding in the same server, and the real-time information synchronization can be achieved without the Date Recue/Date Received 2021-09-27 limitation of the server's TO and CPU memory during the information synchronization procedures.
Brief Description of the Drawings
Detailed Description of an Embodiment
Specifically, as shown in Figure 2, the information synchronization system includes a message management distribution cluster 102 and a message middleware 202. the message management distribution cluster 102 includes a plurality of servers. A plurality of servers are distributed connections, and each server is deployed with spring boot microservice structure. Which means a microservice structure is specifically adopted to deploy a plurality of servers in the message management distribution cluster 102. A plurality of clients respectively publish the messages to the message management distribution cluster 102, and the message management distribution cluster 102 respectively synchronizes messages to a plurality of clients. Specifically, the message management distribution cluster 102 includes a plurality of servers, any server is used to receive the messages and the message topics sent by the clients, publish the messages and the message topics to the message middleware 202, and subscribe the topic messages associated with the message topics from the message middleware 202. When the topic messages associated with the message topics are subscribed from the message middleware 202, the topic messages are synchronously pushed to the corresponding clients. The message middleware 202 is used to receive the topic messages published by any server in the message management distribution cluster 102 and accept subscriptions of the message topics from any server in the message management distribution cluster 102. Among them, the message middleware 202 can include a Date Recue/Date Received 2021-09-27 plurality of databases, wherein the databases constitute a distributed message cache center. Specifically, the message middleware 202 can be a distributed message cache center constituted by a Redis cluster.
Any server integrated the long connection message publication mechanism, and the specific long connection message publication mechanism includes the WebSocket function. Any server adopts WebSocket to build long connection with the clients, adopts WebSocket to receive messages and the message topics sent by the clients, and synchronizes the topic messages to the clients. Any server adopts the map container to record the identity of one or more clients corresponding to each message topics to identify the correspondingly clients, receives and sends the topic message of the message topics to the clients through the clients' correspondingly long connection.
Furthermore, there is no need to continuously maintain a single server, and only need to estimate the number of clients to correspondingly expand the servers in the message management distribution cluster 102, which greatly improves the support capability of information synchronization.
Date Recue/Date Received 2021-09-27
Specifically, each client can build a long connection with a plurality of servers in the message management distribution cluster 102 though a polling distribution method, as shown in Figure 4. Among them, microservice 1 and microservice 2 are respectively referred to two different servers in the message management distribution cluster 102. Each server maintains the connection relationships with the clients in the manner of one message topic maintained by one connection maintenance. Each server maintains all connections between the current server and the clients, and responsible for receiving all messages from the clients and forwarding and synchronizing the messages from the other clients.
Date Recue/Date Received 2021-09-27
Meanwhile, there is no need to achieve the information forwarding and synchronization in the same server, and the real-time information synchronization can be achieved without the limitation of the server's TO and CPU memory during the information synchronization procedures.
S102 includes receiving the message and message topics sent by the clients through the long connection. S106 includes determining the long connection according to the clients' identities, and synchronously pushing the topic message to the clients through the long connection.
Specifically, between the clients and the server, WebSocket is used as the message publication mechanism for the long connection. The clients integrate the WebSocket function, and the server also achieves the WebSocket message receiving function.
building the first long connection with the first client, and building the second long connection with the second client; generating the first identity of the first client, generating the second identity of the second client;
associating the first identity with the first long connection, and associating the second identity with the second long connection. Receiving the messages and the message topics sent by the clients through the long connection including receiving the messages and the message topics sent by the first client through the first long connection and receiving the messages and the message topics sent by the second client through the second long connection.
Determining the long connection Date Recue/Date Received 2021-09-27 according to the clients' identities and pushing the topic messages to the clients synchronously through the long connection including determining the first long connection according to the first identity, and synchronously pushing the topic messages to the first client through the first long connection; determining the second long connection according to the second identity, and synchronously pushing the topic messages to the second client through the second long connection.
Specifically, the server builds a long connection with the first client and the second client respectively, the first long connection is associated with the first client, and the second client is associated with the second long connection. The way of association can be the generation of the identity of each client and establishing the association between the identity and the long connection. When the server receives the messages and the message topics sent by the first client through the first long connection, it records the relationship between the message topics and the first long connection. When the server receives the messages and the message topics sent by the second client through the second long connection, it records the relations of the topic messages and the message topics with the second long connection. When the server subscribes the topic messages associated with the message topics from the message middleware, searches for the clients associated with the message topics and the long connection corresponding to the clients in the local server and sends the topic messages to the corresponding clients through the corresponding long connection. Therefore, the server can connect to a plurality of clients in a balanced way, so that each server can handle a certain number of connections and messages publishing jobs. At this time the server can fully take advantage of the internal resources of TO, CPU, and memory in the local server, and then achieves the efficient information publishing.
and user B acts as client B. Client A edits the document cell D1 and sends the edited data to the message management distribution cluster, collectively referred to below as DCMMCDistributedConnectionMessageManagerCluster. The message format(mesagel) of data sent by a client is as bellow:
{
"baseRevision": 12, "cli entsId": "cb1f27afef924e78a118ec6abbb3dfa3", "docId ": "16538",
"content": "[{"sheetName": "Sheetl", "row": 0, "col": 3, "opType":
"editCell", "value": " edit cell 1", "valueType" : {}, "validator" : {}, "valudeClass": "string", "multi":
falsell", "errorCode": "0", "opType": "editCell", "sheetName": "Sheetl"
DCMMC assigns a client's identity (client id). DCMMC is responsible for managing the long connection of each client, using the mapping of the map to save the client connection which editing the same document. The Date Recue/Date Received 2021-09-27 structure is shown in Figure 7.
Finally, the clients B receives the pushed messagel which displays in the cell, as shown in Figure 10.
The receive module 10 is specifically used to receive the messages and the message topics sent by the first client through the first long connection, and the messages and message topics sent by the second client through the second long connection;
the synchronization module 30 is specifically used to determine the first long connection according to the first identity and push the topic message according to the first long connection;
determine the second long connection according to the second identity and push the topic message to the second client according to the Date Recue/Date Received 2021-09-27 second long connection.
Date Recue/Date Received 2021-09-27
The specific computer device can include more or fewer components than that shown in the figure, or combine certain components, or have different components arrangements.
subscribing the topic messages associated with message topics in the message middleware, and the message middleware is used to receive the topic messages published by any server; When the topic messages associated with the message topics are subscribed from the message middleware, the topic message is synchronously pushed to the clients.
When the processor executes the computer program to implement the above-mentioned steps of receiving the messages and the message topics sent by the clients through the long connection, the following steps are specifically implemented: receiving the message and message topics sent by the first client through the first long connection, receiving the messages and the message topics sent by the second client through the second long connection; the processor executes the computer program to implement the above-mentioned steps of determining the long connection according to the clients' identities, and pushing any topic message synchronously to the clients through the long connection, the following steps are specifically implemented:
the first identity determines the first long connection and pushes any topic message to the first client synchronously through the first long connection; determining the second long connection according to the second identity and pushing any topic message to the second client synchronously through the second long connection.
determining the long connection according to the clients' identities and push any topic message synchronously to the clients through the long connection.
building the first long connection with the first client and building the second long connection with the second client; generating the first identity of the first client and generating the second identity of the second client;
associating the first long connection with the first identity and associating the second long connection with the second identity. When the processor executes the computer program to achieve the above-mentioned steps of receiving the message topics sent by the clients through the long connection, the following steps are specifically implemented: receiving the message topics sent by the first client through the first long connection and receiving the message topics sent by the second client through the second long connection; when the computer program is executed by the processor to implement the above-mentioned steps of determining the long connection according to the clients' identities and pushing any topic message synchronously to the clients through the long connection, the following steps are specifically implemented:
determining the first long connection according to the first identity, pushing any topic message synchronously to the first client through Date Recue/Date Received 2021-09-27 the first long connection; determining the long connection according to the second identity, push any topic message synchronously to the second client through the second long connection.
(EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
Volatile memory can include random access memory (RAM) or external cache memory. As an instruction but not a limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM
(SDRAM), double data rate SDRAM (DDRSDRAM), enhanced type SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic Date Recue/Date Received 2021-09-27 RAM (DRDRAM), and the memory bus dynamic RAM (RDRAM), etc.
Therefore, the appended claims are intended to be construed as encompassing the described embodiment and all the modifications and variations coming into the scope of the disclosure.
Date Recue/Date Received 2021-09-27
Claims (64)
a receiving module configured to:
receive messages and message topics sent by clients;
publish the messages and the message topics to a message middleware, wherein a server subscribes the messages and the message topics from the message middleware, wherein the message middleware is a distribution message cache center, wherein the message middleware receives messages and message topics published by the server;
a subscription module configured to:
subscribe topic messages associated with the message topics from the message middleware, wherein the message middleware receives the topic messages published by the server, wherein the server obtains the topic messages published by the server by subscribing the topic messages of the message topics from the message middleware; and a synchronization module configured to synchronously push the topic messages associated with the message topics to the clients when subscribing the topic messages from the message middleware.
build a long connection with the clients; and generate clients' identities of the clients, associating the long connection with the clients' identities.
Date Recue/Date Received 2023-08-02
determine a long connection according to the clients' identities; and synchronously push the topic messages to the clients through the long connection.
build a first long connection with a first client;
build a second long connection with a second client;
generate a first identity of the first client;
generate a second identity of the second client;
associate the first long connection with the first identity;
associate the second long connection with the second identity.
receive the messages and the message topics sent by a first client through a first long connection; and receive the messages and message topics sent by a second client through a second long connection.
determine a first long connection according to a first identity;
push the topic message according to the first long connection;
determine a second long connection according to a second identity; and Date Recue/Date Received 2023-08-02 push the topic message to a second client according to the second long connection.
use keys of the storage container to record the message topics;
use corresponding values to the keys to record a first client's a first identity and a second client's a second identity.
determine target keys of the storage container according to the message topics when subscribing the topic messages associated with the message topics from the message middleware;
determine the corresponding values according to the target keys;
determine the first and the second identity according to the corresponding values;
determine the first long connection according to the first identity;
synchronously push any topic message to the first client through the first long connection;
determine the second long connection according to the second identity; and synchronously push any topic message to the second client through the second long connection.
Date Recue/Date Received 2023-08-02
Date Recue/Date Received 2023-08-02
a message management distribution cluster;
a message middleware;
wherein the message management distribution cluster includes a plurality of servers, wherein a server is configured to:
receive messages and message topics sent by clients;
publish the messages and message topics to message middleware, wherein the message middleware is a distribution message cache center, wherein the message middleware receives messages and message topics published by the server;
subscribe topic messages associated with the message topics in the message middleware;
Date Recue/Date Received 2023-08-02 push the topic messages synchronously to the clients when the topic messages associated with the message topics are subscribed from the message middleware, wherein the server obtains the topic messages published by the server by subscribing the topic messages of the message topics from the message middleware;
wherein the message middleware is configured to:
receive the topic messages from the server in the message management distribution cluster; and accept a subscription to the message topics published by the server in the message management distribution cluster.
record the message topics from the server;
corresponding values of the keys of the storage container is configured to:
record the clients' identities of microservice requests, wherein the microservice requests send the message topics to the server, wherein the server identifies a clients' long connections through the clients' identities; and send the topic messages to the clients with the message topics through a long connection.
Date Recue/Date Received 2023-08-02
Date Recue/Date Received 2023-08-02 a memory, wherein the memory includes a non-volatile storage medium and an internal memory, wherein the non-volatile storage medium stores an operate system, a computer program, and a database, wherein the internal memory provides an environment for the operating of the operate system and computer program in the non-volatile storage medium;
a processor;
a network interface, configured to connect with external terminals to receive message topics sent by clients and topic messages associated with the message topics;
the database;
the computer program stored in the memory and executed by the processor configured to:
receive messages and the message topics sent by the clients;
publish the messages and the message topics to a message middleware, wherein a server subscribes the messages and the message topics from the message middleware, wherein the message middleware is a distribution message cache center, wherein the message middleware receives messages and message topics published by the server;
subscribe the topic messages associated with the message topics in the message middleware, wherein the message middleware receives the topic messages published by the server, wherein the server obtains the topic messages published by the server by subscribing the topic messages of the message topics from the message middleware; and push the topic message synchronously to the clients, when the message middleware subscribes one of any topic messages associated with the message topics.
Date Recue/Date Received 2023-08-02 building a long connection with the clients;
generating clients' identities of the clients;
associating the long connection with the clients' identities;
the messages and the message topics sent by the clients comprises:
receiving the messages and the message topics sent by the clients through the long connection;
synchronously pushing the topic message to the clients comprises:
determining the long connection according to the clients' identities; and pushing the topic message synchronously to the clients through the long connection.
building a first long connection with the first client;
building a second long connection with the second client;
generating a first identity of the first client;
generating a second identity of the second client; and associating the first long connection with the first identity and associating the second long connection with the second identity.
Date Recue/Date Received 2023-08-02
receiving the messages and the message topics sent by the first client through the first long connection; and receiving the messages and the message topics sent by the second client through the second long connection.
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
creating a storage container of key-value pairs;
using keys of the storage container to record the message topics;
using the values corresponding to the keys to record the first identity of the first client and the second identity of the second client;
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
Date Recue/Date Received 2023-08-02 determining the second long connection according to the second identity;
pushing the topic message synchronously to the second client through the second long connection comprising:
determining target keys of the storage container according to the message topics when the topic messages associated with the message topics are subscribed from the message middleware;
determining the corresponding values according to the target keys;
determining the first identity and the second identity according to the corresponding values;
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
Date Recue/Date Received 2023-08-02
Date Recue/Date Received 2023-08-02
receiving messages and message topics sent by clients;
publishing the messages and the message topics to a message middleware, where a server subscribes the messages and the message topics from the message middleware, wherein the message middleware is a distribution message cache center, wherein the message middleware receives messages and message topics published by the server;
subscribing topic messages associated with the message topics in the message middleware, wherein the message middleware receives the topic messages published by the server, wherein the server obtains the topic messages published by the server by subscribing the topic messages of the message topics from the message middleware; and pushing the topic message synchronously to the clients, when the message middleware subscribes one of any topic messages associated with the message topics.
building a long connection with the clients;
generating clients' identities of the clients;
associating the long connection with the clients' identities;
the messages and the message topics sent by the clients comprises:
receiving the messages and the message topics sent by the clients through the long connection;
synchronously pushing the topic message to the clients comprises:
determining the long connection according to the clients' identities; and pushing the topic message synchronously to the clients through the long connection.
Date Recue/Date Received 2023-08-02
building the first long connection with the first client;
building the second long connection with the second client;
generating a first identity of the first client;
generating a second identity of the second client; and associating the first long connection with the first identity and associating the second long connection with the second identity.
receiving the messages and the message topics sent by the first client through the first long connection; and receiving the messages and the message topics sent by the second client through the second long connection.
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
Date Recue/Date Received 2023-08-02 determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
creating a storage container of key-value pairs;
using keys of the storage container to record the message topics;
using the values corresponding to the keys to record the first identity of the first client and the second identity of the second client;
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity;
pushing the topic message synchronously to the second client through the second long connection comprising:
determining target keys of the storage container according to the message topics when the topic messages associated with the message topics are subscribed from the message middleware;
determining the corresponding values according to the target keys;
determining the first identity and the second identity according to the corresponding values;
determining the first long connection according to the first identity;
Date Recue/Date Received 2023-08-02 pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
Date Recue/Date Received 2023-08-02
receive messages and message topics sent by clients;
publish the messages and the message topics to a message middleware, where a server subscribes the messages and the message topics from the message middleware, wherein the message middleware is a distribution message cache center, wherein the message middleware receives messages and message topics published by the server;
subscribe topic messages associated with the message topics in the message middleware, wherein the message middleware receives the topic messages published by the server, wherein the server obtains the topic messages published by the server by subscribing the topic messages of the message topics from the message middleware; and push the topic message synchronously to the clients, when the message middleware subscribes one of any topic messages associated with the message topics.
building a long connection with the clients;
Date Recue/Date Received 2023-08-02 generating clients' identities of the clients;
associating the long connection with the clients' identities;
the messages and the message topics sent by the clients comprises:
receiving the messages and the message topics sent by the clients through the long connection;
synchronously pushing the topic message to the clients comprises:
determining the long connection according to the clients' identities; and pushing the topic message synchronously to the clients through the long connection.
building the first long connection with the first client;
building the second long connection with the second client;
generating a first identity of the first client;
generating a second identity of the second client; and associating the first long connection with the first identity and associating the second long connection with the second identity.
Date Recue/Date Received 2023-08-02 receiving the messages and the message topics sent by the first client through the first long connection; and receiving the messages and the message topics sent by the second client through the second long connection.
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
creating a storage container of key-value pairs;
using keys of the storage container to record the message topics;
using the values corresponding to the keys to record the first identity of the first client and the second identity of the second client;
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity;
Date Recue/Date Received 2023-08-02 pushing the topic message synchronously to the second client through the second long connection comprising:
determining target keys of the storage container according to the message topics when the topic messages associated with the message topics are subscribed from the message middleware;
determining the corresponding values according to the target keys;
detemnning the first identity and the second identity according to the corresponding values;
determining the first long connection according to the first identity;
pushing the topic message synchronously to the first client through the first long connection;
determining the second long connection according to the second identity; and pushing the topic message synchronously to the second client through the second long connection.
Date Recue/Date Received 2023-08-02
Date Recue/Date Received 2023-08-02
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011052983.5 | 2020-09-29 | ||
CN202011052983.5A CN112351068A (en) | 2020-09-29 | 2020-09-29 | Information synchronization method, system, device, computer equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CA3131954A1 CA3131954A1 (en) | 2022-03-29 |
CA3131954C true CA3131954C (en) | 2023-11-07 |
Family
ID=74361334
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA3131954A Active CA3131954C (en) | 2020-09-29 | 2021-09-27 | Information synchronization method, system, apparatus, computer device and storage medium |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN112351068A (en) |
CA (1) | CA3131954C (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112882987A (en) * | 2021-03-12 | 2021-06-01 | 北京小米移动软件有限公司 | Multi-core communication method and device, electronic equipment and storage medium |
CN113938497A (en) * | 2021-12-17 | 2022-01-14 | 中证信用增进股份有限公司 | Data synchronization method, device and system based on message middleware |
CN114422569A (en) * | 2021-12-30 | 2022-04-29 | 天翼云科技有限公司 | Message pushing method and device of cloud desktop |
CN114827171B (en) * | 2022-03-23 | 2023-12-15 | 青岛中科曙光科技服务有限公司 | Information synchronization method, apparatus, computer device and storage medium |
CN115002213A (en) * | 2022-06-01 | 2022-09-02 | 上海嘉车信息科技有限公司 | Data transmission method and framework |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104811459A (en) * | 2014-01-23 | 2015-07-29 | 阿里巴巴集团控股有限公司 | Processing method, processing device and system for message services and message service system |
CN111131501B (en) * | 2019-12-31 | 2022-03-15 | 郑州信大捷安信息技术股份有限公司 | MQTT protocol-based message pushing system and method |
-
2020
- 2020-09-29 CN CN202011052983.5A patent/CN112351068A/en active Pending
-
2021
- 2021-09-27 CA CA3131954A patent/CA3131954C/en active Active
Also Published As
Publication number | Publication date |
---|---|
CA3131954A1 (en) | 2022-03-29 |
CN112351068A (en) | 2021-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA3131954C (en) | Information synchronization method, system, apparatus, computer device and storage medium | |
RU2471227C2 (en) | Peer-to-peer synchronisation assisted with service unit | |
US10579595B2 (en) | Method and device for calling a distributed file system | |
KR101150146B1 (en) | System and method for managing cached objects using notification bonds | |
CN105138571B (en) | Distributed file system and method for storing massive small files | |
WO2013075578A1 (en) | System and method for offline download of network resource file | |
KR20140038988A (en) | Efficient state reconciliation | |
CN108829720B (en) | Data processing method and device | |
US6918120B2 (en) | Remote file system using network multicast | |
CN109462640B (en) | Metadata synchronization method, data terminal, interaction system and medium | |
WO2016095149A1 (en) | Data compression and storage method and device, and distributed file system | |
CN101442558A (en) | Method and system for providing index service for P2SP network | |
CN114827171B (en) | Information synchronization method, apparatus, computer device and storage medium | |
US20220166842A1 (en) | Data distribution method and electronic device | |
CN113746641B (en) | ODX protocol processing method based on distributed storage | |
CN111193789A (en) | Subscription information pushing method and device, computer equipment and readable storage medium | |
US20200314632A1 (en) | Policy enhancement for mixed capability devices | |
CN114401261A (en) | File downloading method and device | |
CN114254150B (en) | Distributed video storage system and storage method based on block chain | |
CN118075059B (en) | Gateway execution method, device and equipment based on MySQL protocol | |
CN105357222A (en) | Distributed Session management middleware | |
CN113127521B (en) | Full cache scheme and system under distributed system | |
CN112383629B (en) | Method for realizing high-efficiency migratable MQTT Broker subscription tree | |
CN114116889A (en) | Method and device for synchronizing material data, computer equipment and storage medium | |
CN115297130A (en) | Distributed storage network data synchronization method based on block chain |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |
|
EEER | Examination request |
Effective date: 20220428 |