CN103024050B - Distributor and the method that multiple server is distributed - Google Patents

Abstract

A kind of method that the invention discloses distributor and multiple server is distributed.The method comprises: receive user totem information; The unique connection identifier (CID of the overall situation is generated according to user totem information; According to the number of connection identifier (CID and server, the connection that connection identifier (CID indicates is distributed in multiple server; Cloud storage server end issues conditional information and command information when there being Data Update to push server; Push server determines destination client according to this conditional information in multiple browser client, and command information is sent to the socket server corresponding with destination client; Socket server and corresponding browser client are set up socket respectively and are connected, and command information is sent to destination client; Destination client realizes the data syn-chronization of itself and cloud storage server end according to described command information.The present invention can realize the load balance of server, makes system have high suitability when increasing and decreasing server.

Description

Distributor and method for distributing to multiple servers

technical field

The invention relates to the field of information technology data synchronization, in particular to a distributor and a method for distributing multiple servers.

Background technique

At present, with the development of network technology, the Internet, as a huge information resource, has become the most convenient and fast way for people to obtain information. At present, a user usually uses a personal computer to access the Internet (Internet), and accesses a webpage through a browser installed in the personal computer to obtain required information. With the development of mobile communication technologies, users can also access the Internet through mobile terminals supporting browser functions, such as mobile phones and personal digital assistants (Personal Digital Assistant, PDA for short).

However, whether it is a browser on a personal computer or a browser on a mobile terminal, generally no push service is provided, and the information interaction between the server and the client depends on the connection initiated by the client, and the server cannot actively send information to the client , so that real-time synchronization of information between the server and the browser client cannot be realized.

In the prior art, the most commonly used way to synchronize browser data between the browser client and the server is that the browser client sends a request to the server at a certain frequency, such as once a week or once a month. Updates to the information capture this information. However, the applicant found that this data synchronization method has the following technical defects: relatively low efficiency, takes up a lot of resources, and cannot achieve true real-time synchronous update of content.

In a specific implementation manner, the browser client uses the socket server to perform data synchronization with the server, so the browser client needs to maintain a connection with the socket server. However, for a specific browser client, the process of distributing or addressing the corresponding socket server needs to be further optimized.

Contents of the invention

In view of the above problems, the present invention is proposed to provide a distributor and a method of distributing to multiple servers that overcome the above problems or at least partially solve the above problems.

According to one aspect of the present invention, a distributor is provided, which includes: a receiving unit, a connection identifier generating unit, and a distributing unit, wherein:

The receiving unit is adapted to receive user identification information;

The connection identifier generating unit is adapted to generate a globally unique connection identifier according to the user identification information;

The distribution unit is adapted to distribute the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers;

Wherein, the user identification information is included in the connection request sent by the browser client to the distributor, and the distributor further includes a sending unit adapted to send the distributed server ID and connection identifier to the browser server client.

Optionally, the user identification information includes: a user name of a logged-in user and/or a machine hardware identifier of a non-logged-in user.

Optionally, the connection identifier is a specific value within a certain value range.

Optionally, the connection identifier generating unit adopts a cyclic redundancy check algorithm.

Optionally, the cyclic redundancy check algorithm is 32 bits.

Optionally, the distribution unit further includes an average molecular unit, an association subunit and an allocation subunit, wherein:

The average molecular unit is suitable for dividing the numerical range of the connection identifier into multiple numerical intervals according to the number of servers;

The associating subunit is adapted to associate each server with one of the plurality of value intervals;

The allocating subunit is adapted to allocate the connection indicated by the connection identifier to the server associated with its numerical value interval according to the numerical interval in which the connection identifier is located.

Optionally, when the number of servers changes, the distribution unit re-allocates the servers.

Optionally, the server is a socket server.

According to another aspect of the present invention, a method for distributing to multiple servers is provided, the method comprising:

Receive user identification information;

generating a globally unique connection identifier according to the user identification information;

Distributing the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers;

The cloud storage server sends condition information and command information to the push server when there is data update;

The push server determines a target client among multiple browser clients according to the condition information, and sends the command information to a socket server corresponding to the target client;

The socket server establishes a socket connection with the corresponding browser client respectively, and sends the command information to the target client;

The target client implements data synchronization with the cloud storage server according to the command information.

Optionally, the user identification information includes: a user name of a logged-in user and/or a machine hardware identifier of a non-logged-in user.

Optionally, the connection identifier is a specific value within a certain value range.

Optionally, a cyclic redundancy check algorithm is used to generate the connection identifier according to the user identification information.

Optionally, the cyclic redundancy check algorithm is 32 bits.

Optionally, the step of distributing the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers further includes the following substeps:

According to the number of servers, the numerical range of the connection identifier is divided into multiple numerical intervals;

associating each server with one of the plurality of value intervals;

According to the numerical interval in which the connection identifier is located, the connection indicated by the connection identifier is assigned to the server associated with the numerical interval.

Optionally, when the number of servers changes, the servers are reassigned.

Optionally, the server is a socket server.

Optionally, the method further includes the step of the browser client sending a connection request containing the user identification information to the distributor, and after distributing the server, further including the distributor identifying the distributed server and the step of sending the connection identifier to the browser client.

Optionally, the method further includes the step of sending the condition information including the user identification information from the cloud storage server to the push server, and after distributing the information to the server, further includes that the push server sends the condition information with the condition information The step of sending the corresponding command information and the connection identifier to the distributed server.

A distributor and a method for distributing multiple servers according to the present invention can automatically distribute servers in real-time browser synchronization, thereby solving the problem that the existing technology cannot guarantee that each server carries approximately the same number of long connections, That is, the problem that the load balance of the server cannot be realized has achieved the beneficial effects of the load balance of the server, the uniqueness of the distribution result, repeatability, and high adaptability when the system increases or decreases the server.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same components. In the attached picture:

FIG. 1 shows a schematic structural diagram of a system for realizing browser data synchronization according to an embodiment of the present invention;

FIG. 2 shows a schematic structural diagram of a system for implementing browser data synchronization according to an embodiment of the present invention;

Fig. 3 is a schematic diagram of the process of establishing a connection between the browser client and the socket server in the system for realizing browser data synchronization shown in Fig. 2;

Fig. 4 is a schematic diagram of the process of pushing information to the target client in the first type of scenario in the system for realizing browser data synchronization shown in Fig. 2;

Fig. 5 is a schematic diagram of the process of pushing information to the target client in the second type of scenario in the system for implementing browser data synchronization shown in Fig. 2;

Fig. 6 is a schematic diagram of the process of pushing information to the target client in the third type of scenario in the system for realizing browser data synchronization shown in Fig. 2;

7 is a flowchart of a method for implementing browser data synchronization according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a browser client implementing browser data synchronization according to an embodiment of the present invention;

FIG. 9 is a structural diagram of a device for distributing servers according to an embodiment of the present invention;

FIG. 10 is a flow chart of a method for distributing servers according to an embodiment of the present invention; and

Fig. 11 is a schematic diagram of server distribution in the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

In an exemplary embodiment of the present invention, a system for implementing browser data synchronization is provided. As shown in FIG. 1 , the system for synchronizing browser data includes: a cloud storage server 1 , a push server 2 and multiple browser clients 3 and 4 . Among them, the cloud storage server 1 is used to send condition information and command information to the push server when there is data update; the push server 2 is used to determine the target client among multiple browser clients according to the condition information, and send The command information is pushed to the target client 3; the target client 3 is used to realize data synchronization between the target client and the cloud storage server according to the command information.

In the embodiment shown in Figure 1, by setting up a separate push server 2, when the data content stored at the cloud storage server end is updated, the command information is sent to the target client through the push server in time, so that it is simple, Efficiently realize the real-time synchronization of server-side information and client-side information.

As shown in FIG. 1 , multiple browser clients include an initiating client 4 and a target client 3 . Wherein, the initiating client 4 is used to update the data stored in the cloud storage server 1 . The initiating client 4 and the target client 3 may belong to the same user, or may belong to different users. The main application scenario where the initiating client 4 and the target client 3 belong to the same user is: the same user uses different devices (such as a mobile phone and a PC) to log in to the browser, and one of them (such as a PC) changes favorites, then it needs Sync that update to another device (phone) of the same user. An application scenario where the initiating client 4 and the target client 3 do not belong to the same user is, for example, information communication between different browser clients.

Of course, in the present invention, the cloud storage server itself can also initiate an update of the data content. In this case, the initiating browser client 4 in FIG. 1 may not exist. The scenario of this situation is, for example: the system pushes news messages or weather forecasts to all browser clients; or the system initiates an update instruction to all browser clients of a certain version.

Since the cloud storage server 1, the target client 3 and the initiating client 4 within the dotted line box in Figure 1 are existing in the existing browser system, adding a push server on this basis can effectively utilize the original system Architecture, reducing the cost of implementing the present invention.

In order to realize the connection of cloud storage server 1, push server 2 and target client 3, as shown in Figure 2, the system for realizing data synchronization between browser client and cloud storage server can also include multiple socket servers, distribution device.

The distributor is configured to allocate a corresponding socket server and a connection identifier to the client after receiving the connection request, and store the user identification information and the connection identifier in the distribution information database. The detailed connection establishment process is shown in Figure 3, including:

Step S301, the browser client submits a connection request to the distributor. The connection request includes at least user identification information. For a logged-in user, the user identification information may include a user name; for a non-login user, the user identification Information may include the user's machine hardware identification.

For a logged-in user, the user identification information may be a character string. Wherein, in addition to the username of the logged-in user, the character string also includes information such as login time and verification characters. The username is the user unique identification number, which is a number used to represent a user. The verification character is generated according to the user name, and it can be determined whether the user identification information has been changed through the verification character.

For non-logged-in users, the user identification information may include the non-logged-in user's machine hardware ID, where the machine hardware ID is a unique machine ID, which is generated by the client through the hash of the user's machine hardware and system configuration.

In addition, for subsequent target client screening, the connection request may also include user feature information, such as IP address information, browser version information, or user feature information such as user classification information. Wherein, user characteristic information such as browser version number, user classification information, or IP address information can be used for subsequent client screening.

Step S302, the distributor calculates a value based on the user identification information using a preset algorithm, and assigns a socket server to the browser client that submits the connection request according to the value; the value is globally unique, that is, the connection identifier; The distributor sends the connection information such as the IP address and port of the socket server and the connection identifier to the browser client that submitted the request;

In this step, a preset algorithm is used to calculate the above value based on the username of the logged-in user. For a non-login user, the above-mentioned value is directly calculated using the machine hardware identifier of the non-login user, and the algorithm may be a cyclic redundancy check (CRC) 32 algorithm.

Step S303, the browser client establishes a connection with the corresponding socket server according to the received IP address and port number of the socket server, and the connection may be a Transmission Control Protocol (TCP) connection. When the browser client establishes a connection with the socket server, the socket server obtains a resource identifier identifying the connection relationship between the socket server and the browser client. The browser client transmits the received connection identifier to the socket server using the established connection.

Step S304, after the socket server receives the connection identifier, it verifies the connection identifier to the distributor, if the verification is successful, it maintains the connection established with the browser client, and if the verification is unsuccessful, it disconnects connection already established.

Step S305, the distributor stores the user identification information (the user name of the logged-in user or the machine hardware identification of the non-logged-in user), the user characteristic information (if any) and the connection identifier in the distribution information database, and the socket server The resulting resource identifier is also stored in the distribution information database.

It should be noted that, in order to prevent allocation confusion caused by server-side changes, the browser client needs to re-execute steps S301-step S304 to connect after a period of time.

In addition, for each socket server, there is a corresponding separate data table in the distribution information database, so as to reduce the size of the data table and speed up the query speed of the socket server in the subsequent information push stage.

By increasing the distributor and socket server, and setting the distribution information database in the distributor, it is possible to store user identification information, resource identifiers and user characteristic information in the distribution information database during the connection establishment phase, thereby realizing push The server pushes the data content of the preset target client.

In the information push phase: the push server is used to send condition information and command information to the socket server; the socket server is used to forward the information pushed by the push server to the corresponding target client. The detailed information push process is described in detail in the following three types of scenarios.

(1) When the real-time synchronization is initiated by the initiating client, and the initiating client and the receiving client belong to the same user, the condition information includes user identification information. For example, as shown in Figure 4, the information push process includes:

Step S401, initiating the client to update the data stored in the cloud storage server;

In this step, the data stored on the cloud storage server side includes one of the following: favorites information, history information, browser configuration information, note information, login manager information, message reminder information, key information, and other possible information.

Step S402, the cloud storage server sends condition information and command information to the push server, the condition information includes user identification information, such as the user name of the logged-in user or the machine hardware identifier of the user who is not logged in, and the condition information also includes the identification of the initiator the resource identifier of the client's connection to its corresponding socket server;

Step S403, the push server uses the same algorithm as in the distributor to calculate a value based on the user identification information, so as to obtain the socket server assigned to the target client. This value is globally unique, that is, the connection identifier, and the condition Information and command information are sent to the socket server allocated for the target client;

Step S404, the socket server queries the distribution information database in the distributor according to the user identification information in the condition information, and determines the resource identifier corresponding to the target client, excluding those identifying the originating client and its corresponding socket server the resource identifier for the connection;

Step S405, the socket server sends the command information to the target client (one or more) in connection with the target client according to the resource identifier.

(2) When the real-time synchronization is initiated by the initiating client, and the initiating client and the receiving client belong to different login users, that is, the condition information includes user identification information, as shown in Figure 5, the information push process includes:

Step S501, the initiating client initiates updating the data stored in the cloud storage server;

In this step, the data stored on the cloud storage server side includes one of the following: favorites information, history information, browser configuration information, note information, login manager information, message reminder information, key information, news information and/or user Generated information and more.

Step S502, the cloud storage server sends condition information and command information to the push server, where the condition information may include user identification information, such as the user name of a logged-in user or the machine hardware identifier of a non-logged-in user;

Step S503, the push server uses the same algorithm as in the distributor to calculate a value based on the user identification information, so as to obtain the socket server allocated for the target client. This value is globally unique, that is, the connection identifier, and sets the condition Information and command information are sent to the socket server allocated for the target client;

Step S504, the socket server queries the distribution information database in the distributor according to the user identification information in the condition information, and determines the resource identifier of the target client;

Step S505, according to the resource identifier, the corresponding socket server sends the notification message to the target client (one or more) in connection with the client, so far, the information pushing process ends.

(3) When the real-time synchronization is actively initiated by the cloud storage server, and the condition information includes the characteristic screening information of the target client, but does not include the user identification information, wherein the characteristic screening information can also be empty,

In this case, during the connection establishment phase, the connection request submitted by the browser client to the distributor also includes feature screening information, which corresponds to the user feature information stored in the distribution information database as before.

As shown in Figure 6, the information push process includes:

Step S601, the cloud storage server sends condition information and command information to the push server, the condition information includes feature screening information of the target client (such as the version number of a certain browser), and the command information is, for example, an instruction to notify the user to upgrade;

Step S602, the push server pushes the condition information and command information to all socket servers;

Step S603, each socket server submits a query request to the distribution information database of the distributor respectively, and the query request includes characteristic screening information; the distribution information database queries the user characteristic information of each browser client in the distribution information database according to the characteristic screening condition, Determine the resource identifier of the target client satisfying the characteristic filter condition, and return the resource identifier to each socket server that initiates the query;

Step S604, each socket server sends command information to the corresponding client according to the received resource identifier, so far, the information pushing process ends.

In order to further save system resources, the command information pushed by the push server 2 to the browser client 3 is a notification message. In this case, the browser client is also used to establish a connection with the cloud storage server after receiving the notification message pushed by the push server, and download the updated data content from the cloud storage server. Synchronize local data content. By transmitting notification messages, the amount of transmitted data can be reduced, and the occupation of system resources can be reduced.

Of course, the command information pushed by the push server to the target client can also be a content message, that is, the content message contains updated data content. In this case, after the target client receives the content message pushed by the push server, The updated data content is extracted from the content message, and the local data content is synchronized according to the extracted data content. The content message can be directly pushed to the client by transmitting the content message, and the information transmission is fast and the steps are simple.

In order to support multiple languages and call texts conveniently, an HTTP interface is used between the push server and the cloud storage server.

Based on the system for realizing browser data synchronization shown in FIG. 1 and FIG. 2 , the present invention further provides a method for realizing browser data synchronization. As shown in Figure 7, the method for implementing browser data synchronization includes:

Step S710, the cloud storage server sends condition information and command information to the push server when there is data update;

Step S720, the push server determines the target client among multiple browser clients according to the condition information, and sends the command information to the target client;

In step S730, the target client implements data synchronization with the cloud storage server according to the command information.

Further, before step S710, a socket connection is established between the browser client and the socket server, and the establishment process of the connection is shown in FIG. 3 , which will not be repeated here.

Further, in step S710, in the step where the cloud storage server sends condition information and command information to the push server when there is data update, if the condition information includes the user name of the logged-in user of the target client or the machine hardware identifier of the user who is not logged in, including The following two situations:

Situation 1: The originating client and the receiving client belong to the same user, and the user uses different devices (such as a mobile phone and a PC) to log in to the browser, and one of them (such as a PC) changes favorites, then the update needs to be synchronized to the same user's another device (mobile phone);

In this case, the initiating client first initiates modification of information about configurations, functions, or favorites or other information stored in the cloud storage server. Then the cloud storage server sends conditional information and command information to the push server, the command information includes content messages and notification messages, and the push server sends the command information to the target client through the socket server according to the condition information, wherein the target client side excludes the originating client. The information pushing process in this case is shown in FIG. 4 , which will not be repeated here.

Case 2: The initiating client and the receiving client do not belong to the same user, so that information exchange between different users through the client is realized.

Specifically, a user's client sends condition information and content messages to the cloud storage server, and the cloud storage server sends the condition information and related notification messages to the pusher, and the pusher sends the notification message to the destination according to the condition information. The client, and then the target client can access the cloud storage server to obtain content. The information pushing process in this case is shown in FIG. 5 , and will not be repeated here.

In addition, if the conditional information does not include the user identification information of the target client, but may include characteristic screening information, the following situations are also included:

Situation 3: The cloud storage server itself has data updates, and the browser client needs to synchronize data with the cloud storage server. The cloud storage server actively sends condition information and command information to the push server, for example:

1. The cloud storage server sends an update instruction to all browser clients of a certain version, so that all browser clients of this version can be upgraded to a new version, where the command information is a notification message for upgrading to a new version, and the condition is a certain The client version of the browser, that is, the feature filtering information is the version number of the browser client. Then, the push server sending the command information to the target client among the plurality of browser clients according to the condition information includes: the push server sends a notification message of upgrading to a new version to all browser clients of a certain version.

2. The cloud storage server pushes news messages to all browser clients, where the condition is all browser clients, that is, the feature screening information is empty, and the command information is content messages containing news messages; then the push server will send The sending of the command information to the target client among the plurality of browser clients includes: the push server sends the content message including the news message to all the browser clients. It should be understood that what is sent may also be a notification message.

3. The cloud storage server pushes the weather forecast to the browser clients in different regions, where the condition is the browser client in a certain region, that is, the feature screening information is the IP segment corresponding to the certain region, and the command information contains the weather forecast The push server sends the command information to the target client among the plurality of browser clients according to the condition information, including: the push server sends the content message containing the weather forecast to the browser client in a certain area. It should be understood that what is sent may also be a notification message.

The information pushing process in this case is shown in FIG. 6 , which will not be repeated here.

Based on the system for realizing browser data synchronization shown in FIG. 1 and FIG. 2 , the present invention further provides a browser client for realizing browser data synchronization. As shown in Figure 8, the browser client includes: a connection module, used to establish a connection relationship with the socket server through the distributor, and receive command information from the corresponding socket server; Information, execute its corresponding application operation. Wherein, the command information is a notification message or a content message.

As shown in Figure 8, the connection module further includes: a distributor connection submodule, which is used to submit a connection request to the distributor, the connection request at least includes user identification information, and receives the allocated socket returned by the distributor The connection information of the word server and the connection identifier; the socket connection submodule is used to establish a socket connection with the corresponding socket server according to the received connection information of the socket server and the connection identifier, and Receive command information from the corresponding socket server through the socket connection. Wherein, the user identification information is a user name of a login user or a machine hardware identification of a non-login user.

As shown in FIG. 8 , the browser client may further include: a cloud storage communication module, configured to communicate with the cloud storage server in response to an application operation of the application module.

In the browser data synchronization system described above, the following conditions need to be met when distributing socket servers:

1. To achieve load balancing to a certain extent, that is, to achieve approximately the same number of long connections carried by each socket server;

2. The distribution result is unique and repeatable; that is, the distributor assigns the request to a socket server according to the user name of the logged-in user and/or the machine hardware identifier of the non-logged-in user, and the pusher can assign the request to a socket server according to the user name of the logged-in user locating which socket server the current connection is connected to using the username and/or the machine hardware ID of the non-logged-in user;

3. When the system increases or decreases socket servers, the distribution of socket servers should be adaptable, that is, when the system increases or decreases the number of socket servers, it should be possible to complete the redistribution of requests through simple changes .

In order to meet the above distribution conditions, the present invention further proposes a device for distribution to servers. This device may exist in the above-mentioned distributor and pusher and any other equipment and systems that need to distribute to the server.

As shown in FIG. 9, the device includes a receiving unit 910, a connection identifier generating unit 920, and a distributing unit 930, wherein:

The receiving unit 910 is adapted to receive user identification information;

The connection identifier generating unit 920 is adapted to generate a globally unique connection identifier according to the user identification information;

The distribution unit 930 is adapted to distribute the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers.

Wherein, the user identification information includes: the user name of the logged-in user and/or the machine hardware identifier of the non-logged-in user; the connection identifier is used to identify the connection of each client, which is a specific value within a certain value range .

Wherein, the connection identifier generating unit 920 adopts a cyclic redundancy check algorithm, such as a 32-bit cyclic redundancy check algorithm.

In an embodiment of the present invention, the distribution unit 930 further includes an average molecular unit, an association subunit, and an allocation subunit, wherein:

The average molecular unit is suitable for dividing the numerical range of the connection identifier into multiple numerical intervals according to the number of servers;

The associating subunit is adapted to associate each server with one of the plurality of value intervals;

The allocating subunit is adapted to allocate the connection identifier to servers associated with its numerical interval according to the numerical interval in which the connection identifier is located.

When the number of servers changes, the distribution unit 930 can re-allocate the servers.

Optionally, the server is a socket server.

The present invention also provides a distributor, including the above-mentioned device for distributing to multiple servers.

Wherein, the user identification information is included in the connection request sent by the browser client to the distributor, and the distributor further includes a sending unit adapted to send the distributed server ID and connection identifier to the browser server client.

The present invention also provides a push server, including the above-mentioned device for distributing to multiple servers.

Wherein, the user identification information is included in the condition information sent by the cloud storage server to the push server, and the push server further includes a sending unit adapted to send the command information and the connection identifier corresponding to the condition information to the distributed server.

The present invention also provides a distribution system, including the above-mentioned device for distributing to multiple servers.

The system is used to realize browser data synchronization, which includes: cloud storage server, push server, socket server, multiple browser clients and distributor, wherein:

The cloud storage server end is used to send condition information and command information to the push server when there is data update;

The push server is configured to determine a target client among the plurality of browser clients according to the condition information, and send the command information to a socket server corresponding to the target client;

The socket server is configured to respectively establish socket connections with corresponding browser clients, and send command information to target clients; and

The target client is configured to realize data synchronization with the cloud storage server according to the command information;

Distributor for distributing socket servers to browser clients to establish socket connections with;

Wherein, the push server and the distributor include the above-mentioned device for distributing to multiple servers.

The present invention also provides a method for distributing multiple servers in real-time browser synchronization, as shown in Figure 10, the method includes the following steps:

Step S1010, receiving user identification information;

Step S1020, generating a globally unique connection identifier according to the user identification information;

Step S1030, distribute the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers.

Wherein, the user identification information includes: a user name of a logged-in user and/or a machine hardware identifier of a non-logged-in user; and the connection identifier is a specific value within a certain value range.

Wherein, in the step S1020, a cyclic redundancy check algorithm, such as a 32-bit cyclic redundancy check (CRC32) algorithm, may be used to generate a globally unique connection identifier according to the user identification information. The CRC32 algorithm is a consistent hash algorithm, according to which a relatively dynamic, balanced and addressable server distribution method can be realized. In one embodiment of the present invention, according to the CRC32 algorithm, the user name of the logged-in user and/or the machine hardware identifier of the non-logged-in user can be converted into a specific value in the range of 0-2 ³² -1 in a balanced, stable and unique manner.

In an embodiment of the present invention, the step of distributing the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers further includes the following substeps:

According to the number of servers, the numerical range of the connection identifier is divided into multiple numerical intervals;

associating each server with one of the plurality of value intervals;

The connection identifier is allocated to servers associated with its numerical interval according to the numerical interval in which the connection identifier is located.

Wherein, the server is a socket server.

In another embodiment of the present invention, the method further includes the steps of the browser client firstly sending a connection request containing the user identification information to the distributor, and after distributing to the server, further including the distributing The server sends the distributed server identification and connection identifier to the browser client.

In another embodiment of the present invention, the method further includes the step of firstly sending the condition information including the user identification information to the push server from the cloud storage server end, and after distributing to the server, further including the push A step in which the server sends the command information and the connection identifier corresponding to the condition information to the distributed server.

In another embodiment of the present invention, the method also includes the following steps:

The cloud storage server sends condition information and command information to the push server when there is data update;

The push server determines a target client among multiple browser clients according to the condition information, and sends the command information to a socket server corresponding to the target client;

The socket server establishes a socket connection with the corresponding browser client respectively, and sends the command information to the target client;

The target client implements data synchronization with the cloud storage server according to the command information.

The above distribution strategy can be better understood through the server distribution schematic diagram shown in Figure 11. As shown in Figure 11, each connection identifier is hashed into a specific value in the range of 0-2 ³² -1, and distributed in on the circle as shown in the figure. The starting point of the circle is 0, and the ending point is 2 ³² -1.

When the number of servers is three, divide the value range of the connection identifier into three value ranges on average, and assign a value to each of the three servers, for example, if the first server is assigned a value of 0 and 2 ³² -1 , the second server is assigned a value of (2 ³² -1)/3, and the third server is assigned a value of 2*(2 ³² -1)/3. According to the value range that the specific value of the connection identifier falls into, it is assigned to a specific server for processing. For example, values falling between 0 and (2 ³² -1)/3 can be assigned to the first server, values falling between (2 ³² -1)/3 and 2*(2 ³² -1)/3 can be Assigned to the second server, values falling between 2*(2 ³² −1)/3 and 2 ³² −1 may be assigned to the third server.

In addition, when the number of servers changes, the servers are redistributed according to the sub-steps.

For example, when the number of servers is adjusted to 4, the 4 servers can be assigned as 0 and 2 ³² -1, (2 ³² -1)/4, (2 ³² -1)/2, 3*(2 ³² - 1)/4. Then, values falling between 0 and (2 ³² -1)/4 can be assigned to the first server, and values falling between (2 ³² -1)/4 and (2 ³² -1)/2 can be assigned To the second server, values falling between (2 ³² -1)/2 and 3*(2 ³² -1)/4 can be assigned to the third server, falling between 3*(2 ³² -1)/4 and A value between 2 ³² -1 can be assigned to the fourth server.

The above method for distributing servers can be applied to the browser real-time synchronization system introduced above and other systems that need to distribute servers.

In summary, the present invention realizes dynamic, balanced and addressable server distribution. The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components in related devices according to the embodiments of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

Claims (18)

1. A distributor, comprising: a receiving unit, a connection identifier generating unit and a distributing unit, wherein: The receiving unit is adapted to receive user identification information; The connection identifier generating unit is adapted to generate a globally unique connection identifier according to the user identification information; wherein the connection identifier is used to identify the connection of each browser client; The distribution unit is adapted to distribute the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers; Wherein, the user identification information is included in the connection request sent by the browser client to the distributor, and the distributor further includes a sending unit adapted to send the distributed server ID and connection identifier to the browser server client. 2. The distributor according to claim 1, wherein the user identification information comprises: a user name of a logged-in user and/or a machine hardware ID of a non-logged-in user. 3. The distributor of claim 1, wherein the connection identifier is a specific value within a certain range of values. 4. The distributor according to claim 1, wherein the connection identifier generating unit employs a cyclic redundancy check algorithm. 5. The distributor of claim 4, wherein the cyclic redundancy check algorithm is 32 bits. 6. The dispenser of claim 1, wherein the distribution unit further comprises an average molecular unit, an association subunit and an allocation subunit, wherein: The average molecular unit is suitable for dividing the numerical range of the connection identifier into multiple numerical intervals according to the number of servers; The associating subunit is adapted to associate each server with one of the plurality of value intervals; The allocating subunit is adapted to allocate the connection indicated by the connection identifier to the server associated with its numerical value interval according to the numerical interval in which the connection identifier is located. 7. The distributor according to claim 1, wherein when the number of servers changes, the distribution unit reassigns the servers. 8. The distributor of claim 1, wherein the server is a socket server. 9. A method for distributing to multiple servers, the method comprising: Receive user identification information; Generate a globally unique connection identifier according to the user identification information; wherein, the connection identifier is used to identify the connection of each browser client; Distributing the connection indicated by the connection identifier to one of the plurality of servers according to the connection identifier and the number of servers; The cloud storage server sends condition information and command information to the push server when there is data update; The push server determines a target client among multiple browser clients according to the condition information, and sends the command information to a socket server corresponding to the target client; The socket server establishes a socket connection with the corresponding browser client respectively, and sends the command information to the target client; The target client implements data synchronization with the cloud storage server according to the command information. 10. The method according to claim 9, wherein the user identification information comprises: a user name of a logged-in user and/or a machine hardware ID of a non-logged-in user. 11. The method of claim 9, wherein the connection identifier is a specific value within a certain range of values. 12. The method according to claim 9, wherein the connection identifier is generated according to the user identification information using a cyclic redundancy check algorithm. 13. The method of claim 12, wherein the cyclic redundancy check algorithm is 32 bits. 14. The method according to claim 9, wherein, according to the connection identifier and the number of servers, the step of distributing the connection indicated by the connection identifier to one of the plurality of servers further comprises the following substeps: According to the number of servers, the numerical range of the connection identifier is divided into multiple numerical intervals; associating each server with one of the plurality of value intervals; According to the numerical interval in which the connection identifier is located, the connection indicated by the connection identifier is assigned to the server associated with the numerical interval. 15. The method of claim 14, wherein when the number of servers changes, the servers are reassigned. 16. The method of claim 9, wherein the server is a socket server. 17. The method according to any one of claims 9-16, wherein the method further comprises the steps of the browser client sending a connection request containing the user identification information to the distributor, and performing After the distribution, it also includes the step of the distributor sending the distributed server identification and connection identifier to the browser client. 18. The method according to any one of claims 9-16, wherein the method further comprises the step of sending the condition information containing the user identification information from the cloud storage server to the push server, and performing After the distribution, the push server further includes the step of sending the command information and the connection identifier corresponding to the condition information to the distributed server.