CN109743345B - Data sending and receiving method, device, server and client - Google Patents
Data sending and receiving method, device, server and client Download PDFInfo
- Publication number
- CN109743345B CN109743345B CN201811372142.5A CN201811372142A CN109743345B CN 109743345 B CN109743345 B CN 109743345B CN 201811372142 A CN201811372142 A CN 201811372142A CN 109743345 B CN109743345 B CN 109743345B
- Authority
- CN
- China
- Prior art keywords
- client
- identifier
- state
- service interface
- server
- 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
Images
Landscapes
- Telephonic Communication Services (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a data sending and receiving method, a device, a server and a client, wherein the sending method comprises the following steps: receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface; judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface; if yes, sending the second state identification to the client, and if not, sending the first state identification to the client so that the client determines whether to request a service interface according to the received state identification; and when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface. By adopting the technical scheme provided by the embodiment of the invention, the request quantity of the service interface can be reduced, and the impact on the service interface can be reduced.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data sending method, a data receiving method, a data sending device, a data receiving device, a server, and a client.
Background
The server of the internet application can provide service for the client of the internet application through the service interface, and the client can obtain data provided by the service interface through the request service interface, so that the data access of the client to the internet application is realized. When the data provided by the service interface changes, the client needs to request the service interface again to obtain the changed data provided by the service interface.
In the prior art, a client generally requests a service interface at a preset time interval, so as to obtain changed data provided by the service interface after the data provided by the service interface is changed.
However, the inventor finds that the prior art has at least the following problems in the process of implementing the invention: due to limited server resources, if the request amount of the client to the service interface is large, the impact on the service interface is likely to be large, and the probability of service unavailability is increased.
Disclosure of Invention
Embodiments of the present invention provide a data sending and receiving method, an apparatus, a server, and a client, so as to reduce a request amount of the client to a service interface, thereby reducing impact on the service interface and reducing a probability of unavailability of a service. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a data sending method, which is applied to a server, and the method includes:
receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface of the server and is locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface;
if yes, the second state identification is sent to the client, and if not, the first state identification is sent to the client, so that the client determines whether to request the service interface according to the received state identification;
and when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface.
Optionally, the determining whether to send the second state identifier to the client includes:
judging whether to send a second state identification to the client according to a preset probability; or
Judging whether to send a second state identifier to the client according to whether the release time of the client is within a first preset time period; or
And judging whether to send a second state identifier to the client according to the equipment identifier of the equipment where the client is located.
Optionally, before the determining whether to send the second state identifier to the client, the method further includes:
judging whether the second state identifier is the same as the first state identifier or not;
if the state identifiers are the same, the second state identifier is sent to the client;
and if not, executing the step of judging whether to send the second state identification to the client.
Optionally, the receiving a status request including a first status identifier sent by a client includes:
receiving a state request which is sent to a state interface by a client and contains a first state identifier, wherein the state interface stores the state identifiers of all service interfaces of the server;
the sending the second state identifier to the client includes:
and sending the second state identifier stored in the state interface to the client through the state interface.
Optionally, before the determining whether to send the second state identifier to the client, the method further includes:
judging whether the current time is within a second preset time period or not;
if not, sending a second state identification to the client;
and if so, executing the step of judging whether to send the second state identification to the client.
In a second aspect, an embodiment of the present invention further provides a data receiving method, which is applied to a client, where the method includes:
when a specific opportunity is reached, sending a state request containing a first state identifier to a server, wherein the first state identifier is a state identifier of a service interface of the server and locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
receiving a state identifier sent by the server according to a judgment result, wherein the judgment result is as follows: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
judging whether the received state identification is the same as the first state identification or not;
and if not, requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface.
Optionally, the sending the status request including the first status identifier to the server includes:
sending a state request containing a first state identifier to a state interface of a server, wherein the state interface is used for storing the state identifiers of all service interfaces of the server;
correspondingly, the receiving the state identifier sent by the server according to the judgment result includes:
and receiving the state identifier sent by the server through the state interface according to the judgment result.
In a third aspect, an embodiment of the present invention further provides a data sending apparatus, which is applied to a server, where the apparatus includes:
a request receiving unit, configured to receive a status request that includes a first status identifier and is sent by a client, where the first status identifier is a status identifier of a service interface of the server and is locally stored by the client, and the status identifier is an identifier used to represent status information of data provided by the service interface;
a sending judgment unit, configured to judge whether to send a second state identifier to the client, where the second state identifier is a latest state identifier of the service interface;
a first identifier sending unit, configured to send the second status identifier to the client when the determination result of the sending determination unit is yes, and send the first status identifier to the client when the determination result of the sending determination unit is no, so that the client determines whether to request the service interface according to the received status identifier;
and the data sending unit is used for sending the data provided by the service interface to the client through the service interface when receiving the request of the client to the service interface.
Optionally, the sending determining unit is specifically configured to:
judging whether to send a second state identification to the client according to a preset probability; or
Judging whether to send a second state identifier to the client according to whether the release time of the client is within a first preset time period; or
And judging whether to send a second state identifier to the client according to the equipment identifier of the equipment where the client is located.
Optionally, the apparatus further comprises:
a first identifier determining unit configured to determine whether a second status identifier is the same as the first status identifier;
a second identifier sending unit, configured to send the second state identifier to the client when the determination result of the first identifier determining unit is yes;
correspondingly, the sending judging unit is specifically configured to judge whether to send the second state identifier to the client when the judgment result of the first identifier judging unit is negative.
Optionally, the request receiving unit is specifically configured to receive a status request that is sent by a client to a status interface and includes a first status identifier, where the status interface stores status identifiers of service interfaces of the server;
the first identifier sending unit is specifically configured to send the second status identifier stored in the status interface to the client through the status interface.
Optionally, the apparatus further comprises:
the time judging unit is used for judging whether the current time is within a second preset time period;
a third identifier sending unit, configured to send a second state identifier to the client when the determination result of the time determination unit is negative;
the sending judging unit is specifically configured to judge whether to send the second state identifier to the client when the judgment result of the time judgment unit is yes.
In a fourth aspect, an embodiment of the present invention further provides a data receiving apparatus, which is applied to a client, where the apparatus includes:
a request sending unit, configured to send, when a certain opportunity is reached, a status request including a first status identifier to a server, where the first status identifier is a status identifier of a service interface of the server and locally stored by the client, and the status identifier is an identifier used to represent status information of data provided by the service interface;
an identifier receiving unit, configured to receive a status identifier sent by the server according to a determination result, where the determination result is: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
a second identifier determining unit configured to determine whether the received status identifier is the same as the first status identifier;
and the data receiving unit is used for requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface when the judgment result of the second identification judging unit is negative.
Optionally, the request sending unit is specifically configured to send a status request including a first status identifier to a status interface of a server when a specific time is reached, where the status interface is used to store status identifiers of each service interface of the server;
correspondingly, the identification receiving unit receives the state identification sent by the server through the state interface according to the judgment result.
In a fifth aspect, an embodiment of the present invention further provides a server, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus;
the memory is used for storing a computer program;
the processor is configured to implement the method steps of any of the first aspect when executing the program stored in the memory.
In a sixth aspect, an embodiment of the present invention further provides a client, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus;
the memory is used for storing a computer program;
the processor, when executing a program stored in the memory, is adapted to carry out the method steps of any of the second aspect of the claims.
In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is caused to execute any of the data transmission methods described above.
In an eighth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is caused to execute any one of the data receiving methods described above.
In a ninth aspect, an embodiment of the present invention further provides a computer program product including instructions, which when run on a computer, causes the computer to execute any one of the data transmission methods described above.
In a tenth aspect, embodiments of the present invention further provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any of the above-mentioned data receiving and sending methods.
According to the data sending and receiving method, the data sending and receiving device, the server and the client, the server receives the status request sent by the client, the status request contains the first status identifier, the server sends the second status identifier to the client when judging that the second status identifier is sent to the client, and the server sends the first status identifier to the client when judging that the second status identifier is not sent to the client. And because the first state identifier is the state identifier of the service interface of the server locally stored by the client, the second state identifier is the latest state identifier of the service interface, and the state identifier represents the state information of the data provided by the service interface, when the client receives the first state identifier, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, so that the request quantity of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a schematic flowchart of a first method for sending data according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a second method for sending data according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a third method for sending data according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a fourth flowchart of a data transmission method according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a data receiving method according to an embodiment of the present invention;
fig. 6 is a schematic flowchart of another data receiving method according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a data receiving apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a client according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
In order to reduce the request amount of a client to a service interface, thereby reducing the impact on the service interface and reducing the probability of unavailable service, the embodiment of the invention provides a data sending and receiving method, a device, a server and a client
First, a data transmission method provided in an embodiment of the present invention is described below.
It should be noted that the data transmission method provided by the embodiment of the present invention may be applied to the internet industry.
As shown in fig. 1, a data transmission method provided in an embodiment of the present invention includes the following steps:
s110: and receiving a state request which is sent by the client and contains the first state identification.
The first state identification is the state identification of the service interface of the server stored locally by the client, and the state identification is the identification of state information used for representing data provided by the service interface.
It will be appreciated that the data provided by the service interface changes, i.e. the data of the data source of the service corresponding to the service interface changes.
In one implementation manner of the present invention, the server may receive a status request containing a first status identifier, which is sent to the server by the client when a specific opportunity is reached. The specific time may be: the method comprises the following steps of restarting a client, reinstalling an application, reaching a preset time interval, and switching the application from a background interface to a foreground interface, wherein the application can be an application which is installed in the client and corresponds to a service interface.
In an implementation manner of the present invention, the server may determine the status identifier of the service interface according to whether the data provided by the service interface changes. Specifically, the server may determine whether data provided by the service interface changes, and if so, determine the status identifier of the service interface as an identifier different from any status identifier before the data provided by the service interface changes. For example, before the data provided by the service interface changes, the status identifier of the service interface is "1", if the server determines that the data provided by the service interface changes, the status identifier of the service interface is determined to be "2", and after the status identifier of the service interface is determined to be "2", if the server determines that the data provided by the service interface changes again, the status identifier of the service interface may be determined to be "3". Those skilled in the art may set a specific form of the status identifier of the service interface according to actual situations, and the embodiment of the present invention is not particularly limited.
Optionally, the state identifier of the service interface of the server, which is locally stored by the client, may be a state identifier of the service interface, which is updated when the client requests the service interface. Specifically, the state identifier of the service interface of the server locally stored by the client may be: the client acquires and stores the state identifier of the service interface at the local place when requesting the service interface last time, or the client acquires and stores the state identifier of the service interface at the local place when requesting the service interface before receiving the state identifier sent by the server. In the embodiment of the present invention, the client may store the state identifier of the service interface on a local hard disk, or cache the state identifier of the service interface in a local memory.
S120: and judging whether to send the second state identification to the client.
Wherein the second state identification is the latest state identification of the service interface.
In one embodiment, the server may determine whether to send the second state identifier to the client with a preset probability. The preset probability can be any probability smaller than 1, for example, the preset probability can be any probability from 0.2 to 0.8. Specifically, when the preset probability is 0.6, the server may determine whether to send the second state identifier to the client according to the probability of 0.6, so that the server determines that the probability of sending the second state identifier to the client is 0.6, and determines that the probability of not sending the second state identifier to the client is 0.4. And judging whether to send the second state identification to the client side according to the preset probability, and simply and quickly determining whether to send the second state identification to the client side.
In another embodiment, the server may also determine whether to send the second state identifier to the client according to whether the publishing time of the client is within a first preset time period, and correspondingly, the state request may further include the publishing time of the client. Specifically, when the server judges that the release time of the client is within a first preset time period, the server judges to send the second state identifier to the client. The first preset time period may be a time period shorter than a preset time period from the current time, the preset time period may be any time period from 1 day to 10 days, or any time period from 2 hours to 24 hours, for example, and a person skilled in the art may also set other time periods as the preset time period according to an actual situation, which is not particularly limited in the embodiment of the present invention. The release time may be a time when the client installs the application corresponding to the service interface. The embodiment judges whether to send the second state identification to the client according to the release time of the client, and can send the second state identification to the clients with different release times more flexibly, so that the clients with different release times can receive different data provided by the service interface, and the data can be sent more flexibly. When the first preset time period is a time period which is shorter than the preset time from the current moment, the recently issued client can receive the changed data provided by the service interface more timely, and the user experience of a new user can be improved.
In other manners, the server may also determine whether to send the second status identifier to the client according to the device identifier of the device where the client is located, and correspondingly, the status request may further include the device identifier of the device where the client is located. The device identifier may be any one of an International Mobile Equipment Identity (IMEI) and a hardware address (MAC), or may be another device identifier for marking a device. For example, the server may determine whether to send the second state identifier to the client according to the tail number of the device identifier of the device where the client is located, and specifically, the server may send the second state identifier to the client whose tail number of the device identifier of the device where the client is located is an odd number or an even number. Whether the second state identification is sent to the client side can be judged more quickly according to the equipment identification of the equipment, and therefore the data sending speed is improved.
S130: if the judgment result in the step S120 is yes, the second status identifier is sent to the client, and if the judgment result in the step S120 is no, the first status identifier is sent to the client, so that the client determines whether to request the service interface according to the received status identifier.
Specifically, the server sends the state identifier of the service interface to the client, so that the client can judge whether the received state identifier is the same as the first state identifier after receiving the state identifier sent by the server; if not, the service interface is requested, the service interface feeds back the data provided by the service interface to the client after receiving the request, and then the client receives the data provided by the service interface fed back by the server through the service interface.
S140: and when a request of the client for the service interface is received, sending the data provided by the service interface to the client through the service interface.
According to the data transmission method provided by the embodiment of the invention, the first state identifier is the state identifier of the service interface of the server locally stored by the client, and the second state identifier is the latest state identifier of the service interface, so that when the client receives the first state identifier, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, and the request amount of the client to the service interface can be reduced, so that the impact on the service interface is reduced, and the probability of service unavailability is reduced.
In order to increase the data transmission speed, in one embodiment, as shown in fig. 2, before step S120, the following steps S150 to S160 may be further included:
s150: judging whether the second state identifier is the same as the first state identifier or not;
s160: if the judgment result in the step S150 is yes, sending a second state identifier to the client;
correspondingly, if the determination result in step S150 is negative, the above-mentioned step S120 is executed to determine whether to send the second status flag to the client.
Wherein, the second status flag in step S150 is the latest status flag of the service interface.
In the embodiment of the present invention, when the second state identifier is the same as the first state identifier, it indicates that the latest state identifier of the service interface is the same as the state identifier of the service interface locally stored by the client, and it indicates that data provided by the service interface has not changed, at this time, the second state identifier may be directly sent to the client. The steps executed by data sending can be reduced, the state identification is sent to the client more quickly, and the data sending speed is further improved.
In order to facilitate the management of the state identifier of each service interface by the server, in an embodiment, as shown in fig. 3, step S110 may be implemented as the following step S111:
s111: receiving a state request which is sent to a state interface by a client and contains a first state identifier, wherein the state identifiers of all service interfaces of a server are stored in the state interface;
accordingly, step S130 can be implemented as the following step S131:
s131: and if the judgment result in the step S120 is yes, sending the second state identifier stored in the state interface to the client through the state interface, and if the judgment result in the step S120 is no, sending the first state identifier to the client through the state interface, so that the client determines whether to request the service interface according to the received state identifier.
In the embodiment of the invention, the state interface is arranged in the server, the state identifiers of all the service interfaces of the server are stored in the state interface, and when the client requests the state interface, the state identifiers of the service interfaces can be obtained, so that the client can more quickly and efficiently obtain the state identifiers of all the service interfaces, and meanwhile, when the server has a plurality of service interfaces, the state identifiers of a plurality of service interfaces can be managed on one state interface, thereby being more convenient for the server to manage the state identifiers of all the service interfaces.
In one embodiment, as shown in fig. 4, before step S120, the following steps S170 to S180 may be further included:
s170: judging whether the current time is within a second preset time period or not;
s180: if the judgment result of the step S170 is negative, sending a second state identifier to the client;
accordingly, step S120 can be implemented as follows: if the judgment result in the step S170 is yes, it is judged whether to send the second status flag to the client.
The second predetermined time period may be determined according to a peak time period of the client's access to the server, for example, when the peak time period of the client's access to the server is 19: 00-22: 00, the second preset time period may be 19: 00-22: 00, the person skilled in the art can set the second preset time period according to the actual situation.
When the current time is not within the second preset time period, the embodiment of the invention shows that the access amount of the current client to the server is low, and at the moment, the second state identifier can be directly sent to the client, so that the client can more timely acquire the changed data provided by the service interface.
Optionally, when the determination result in step S170 is yes, the server may further determine whether the requested frequency of the service interface is higher than a preset frequency, and if so, screen the request in the status interface, and determine whether to return the latest status identifier of the service interface to the client according to the screening result, so as to reduce the request of the client to the service interface. The screening can be realized in any one of the following modes: and screening according to the preset random probability and the equipment identification corresponding to the client. Since the server resources allocated to the service corresponding to the service interface with the smaller request frequency are generally less, the probability that the service corresponding to the service interface with the smaller request frequency is unavailable during the peak period is higher. In this way, the probability of low frequency service unavailability due to less allocated server resources can be more specifically reduced during peak hours. In addition, because the data change frequency provided by the service interface of the low-frequency service is greatly different from the data change frequency provided by the service interface of the high-frequency service, the high-frequency service and the low-frequency service can be distinguished by the mode, and different data transmitting/receiving strategies are used for the high-frequency service and the low-frequency service, so that the data transmission/reception is more flexible.
Corresponding to the data sending method, the embodiment of the invention also provides a data receiving method.
As shown in fig. 5, the data sending method provided in the embodiment of the present invention is applied to a client, and includes the following steps:
s210: and when a specific opportunity is reached, sending a state request containing the first state identifier to the server.
The first state identifier is a state identifier of a service interface of the server stored locally by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface.
In the embodiment of the invention, the client can send the state request containing the first state identifier to the server when a specific opportunity is reached. The specific time may be: the method comprises the following steps of restarting a client, reinstalling an application, reaching a preset time interval, and switching the application from a background interface to a foreground interface, wherein the application can be an application which is installed in the client and corresponds to a service interface.
In the embodiment of the present invention, the server may determine the status identifier of the service interface according to whether the data provided by the service interface changes. Specifically, the server may determine whether data provided by the service interface changes, and if so, determine the status identifier of the service interface as an identifier different from any status identifier before the data provided by the service interface changes.
Optionally, the state identifier of the service interface of the server, which is locally stored by the client, may be a state identifier of the service interface, which is updated when the client requests the service interface. Specifically, the state identifier of the service interface of the server locally stored by the client may be: the client acquires and stores the state identifier of the service interface at the local place when requesting the service interface last time, or the client acquires and stores the state identifier of the service interface at the local place when requesting the service interface before receiving the state identifier sent by the server. In the embodiment of the present invention, the client may store the state identifier of the service interface on a local hard disk, or cache the state identifier of the service interface in a local memory.
S220: and receiving the state identifier sent by the server according to the judgment result.
Wherein, the above-mentioned judged result is: the server judges whether to send the result of the second state identification to the client, if the judgment result is yes, the server sends the second state identification to the client, if the judgment result is no, the server sends the first state identification to the client, and the second state identification is the latest state identification of the service interface.
In an embodiment of the present invention, the determination result may be specifically: the server judges whether to send a result of the second state identification to the client according to a preset probability; or the server judges whether to send the result of the second state identification to the client according to whether the release time of the client is within the first preset time period; or the server also judges whether to send the result of the second state identifier to the client according to the device identifier of the device where the client is located.
S230: and judging whether the received state identifier is the same as the first state identifier or not.
S240: if the judgment result in the step S230 is negative, the service interface is requested, and the data provided by the service interface, which is fed back by the server through the service interface, is received.
For example, the state identifier of the service interface locally stored by the first client is "1", that is, the first state identifier of the first client is "1", the state identifier of the service interface locally stored by the second client is "2", that is, the first state identifier of the second client is "2", the latest state identifier of the service interface of the server is "3", that is, the second state identifier is "3", the state identifier sent by the first client receiving server according to the determination result is "3", and the state identifier sent by the second client receiving server according to the determination result is "2", then, the first client may determine that the received state identifier is different from the first state identifier, the second client may determine that the received state identifier is the same as the first state identifier, and the second client may not request the service interface.
In the data receiving method provided by the embodiment of the invention, because the first state identifier is the state identifier of the service interface of the server locally stored by the client and the second state identifier is the latest state identifier of the service interface, when the client receives the first state identifier, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, and thus the request amount of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
In an embodiment, the data receiving method may further include the following steps: if the determination result in the step S230 is negative, the state identifier of the service interface of the server locally stored by the client is updated to the received state identifier. The client updates the state identifier of the locally stored service interface into the received state identifier, so that the state identifier of the locally stored service interface of the client can be updated in time, the number of invalid requests is reduced, and the occupation of server resources is further reduced.
In one embodiment, as shown in fig. 6, step S210 may be implemented as the following step S211:
s211: when a specific time is reached, sending a state request containing a first state identifier to a state interface of the server, wherein the state interface is used for storing the state identifiers of all service interfaces of the server;
accordingly, step S220 may be implemented as the following step S221:
s221: and receiving the state identifier sent by the server through the state interface according to the judgment result.
In the embodiment of the invention, the state interface is arranged in the server, the state identifiers of all the service interfaces of the server are stored in the state interface, and when the client requests the state interface, the state identifiers of the service interfaces can be obtained, so that the client can more quickly and efficiently obtain the state identifiers of all the service interfaces, and meanwhile, when the server has a plurality of service interfaces, the state identifiers of a plurality of service interfaces can be managed on one state interface, thereby being more convenient for the server to manage the state identifiers of all the service interfaces.
An embodiment of the present invention further provides a data sending apparatus, which is applied to a server, and as shown in fig. 7, the apparatus may include:
a request receiving unit 310, configured to receive a status request sent by a client and containing a first status identifier, where the first status identifier is a status identifier of a service interface of the server and stored locally by the client, and the status identifier is an identifier of status information representing data provided by the service interface;
a sending determining unit 320, configured to determine whether to send a second status identifier to the client, where the second status identifier is a latest status identifier of the service interface;
a first identifier sending unit 330, configured to send the second status identifier to the client when the determination result of the sending determining unit 320 is yes, and send the first status identifier to the client when the determination result of the sending determining unit 320 is no, so that the client determines whether to request the service interface according to the received status identifier;
the data sending unit 340 may be configured to send, when receiving a request from the client for the service interface, data provided by the service interface to the client through the service interface.
According to the data sending device provided by the embodiment of the invention, because the first state identifier is the state identifier of the service interface of the server locally stored by the client and the second state identifier is the latest state identifier of the service interface, when the client receives the first state identifier sent by the server, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, so that the request quantity of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
In an embodiment, the sending determining unit 320 may be specifically configured to:
judging whether to send a second state identification to the client according to a preset probability; or
Judging whether to send a second state identifier to the client according to whether the release time of the client is within a first preset time period; or
And judging whether to send a second state identifier to the client according to the equipment identifier of the equipment where the client is located.
In one embodiment, the apparatus may further include:
a first identifier determining unit configured to determine whether a second status identifier is the same as the first status identifier;
a second identifier sending unit, configured to send the second state identifier to the client when the determination result of the first identifier determining unit is yes;
correspondingly, the sending determining unit 320 may be specifically configured to determine whether to send the second status identifier to the client when the determination result of the first identifier determining unit is negative.
In an implementation manner, the request receiving unit 310 may be specifically configured to receive a status request that is sent by a client to a status interface and includes a first status identifier, where the status interface stores status identifiers of service interfaces of the server;
the first identifier sending unit 330 may be specifically configured to send the second state identifier stored in the state interface to the client through the state interface.
In one embodiment, the apparatus may further include:
the time judging unit is used for judging whether the current time is within a second preset time period;
a third identifier sending unit, configured to send a second state identifier to the client when the determination result of the time determination unit is negative;
the sending determining unit 320 may be specifically configured to determine whether to send the second status identifier to the client when the determination result of the time determination list is yes.
An embodiment of the present invention further provides a data receiving apparatus, which is applied to a client, and as shown in fig. 8, the apparatus includes:
a request sending unit 410, configured to send, when a certain occasion is reached, a status request including a first status identifier to a server, where the first status identifier is a status identifier of a service interface of the server and stored locally by a client, and the status identifier is an identifier used to represent status information of data provided by the service interface;
the identifier receiving unit 420 may be configured to receive a status identifier sent by the server according to a determination result, where the determination result is: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
a second identifier determining unit 430, configured to determine whether the received status identifier is the same as the first status identifier;
the data receiving unit 440 may be configured to request the service interface and receive data provided by the service interface and fed back by the server through the service interface when the determination result of the second identifier determining unit 430 is negative.
According to the data receiving device provided by the embodiment of the invention, because the first state identifier is the state identifier of the service interface of the server locally stored by the client and the second state identifier is the latest state identifier of the service interface, when the client receives the first state identifier, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, so that the request quantity of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
In an embodiment, the request sending unit 410 may be specifically configured to send, when a specific occasion is reached, a status request including a first status identifier to a status interface of a server, where the status interface is used to store status identifiers of service interfaces of the server;
correspondingly, the identifier receiving unit 420 may be specifically configured to receive the status identifier sent by the server through the status interface according to the determination result.
The embodiment of the present invention further provides a server, as shown in fig. 9, including a processor 501, a communication interface 502, a memory 503 and a communication bus 504, where the processor 501, the communication interface 502 and the memory 503 complete mutual communication through the communication bus 504,
a memory 503 for storing a computer program;
the processor 501, when executing the program stored in the memory 503, implements the following steps:
receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface of the server and is locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface;
if yes, the second state identification is sent to the client, and if not, the first state identification is sent to the client, so that the client determines whether to request the service interface according to the received state identification;
and when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface.
According to the server provided by the embodiment of the invention, because the first state identifier is the state identifier of the service interface of the server locally stored by the client and the second state identifier is the latest state identifier of the service interface, when the client receives the first state identifier sent by the server, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the service interface locally stored, so that the request quantity of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
The embodiment of the present invention further provides a client, as shown in fig. 10, which includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, where the processor 601, the communication interface 602, and the memory 603 complete mutual communication through the communication bus 604,
a memory 603 for storing a computer program; the processor 601 is configured to implement the following steps when executing the program stored in the memory 603:
when a specific opportunity is reached, sending a state request containing a first state identifier to a server, wherein the first state identifier is a state identifier of a service interface of the server and locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
receiving a state identifier sent by the server according to a judgment result, wherein the judgment result is as follows: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
judging whether the received state identification is the same as the first state identification or not; and if not, requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface.
When the client receives the first state identifier, the first state identifier is the state identifier of the service interface of the server locally stored by the client, and the second state identifier is the latest state identifier of the service interface, so that the state identifier received by the client is the same as the state identifier of the service interface locally stored, the client considers that data provided by the service interface is unchanged, and does not send a request to the service interface, and further the request amount of the client to the service interface can be reduced, so that the impact on the service interface is reduced, and the probability of service unavailability is reduced.
The communication bus mentioned above for the server and the client may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
An embodiment of the present invention further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is run on a computer, the computer is caused to execute the following method steps:
receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface of the server and is locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface;
if yes, the second state identification is sent to the client, and if not, the first state identification is sent to the client, so that the client determines whether to request the service interface according to the received state identification;
and when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface.
An embodiment of the present invention further provides a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is run on a computer, the computer is caused to execute the following method steps:
when a specific opportunity is reached, sending a state request containing a first state identifier to a server, wherein the first state identifier is a state identifier of a service interface of the server and locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
receiving a state identifier sent by the server according to a judgment result, wherein the judgment result is as follows: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
judging whether the received state identification is the same as the first state identification or not; and if not, requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface.
In the storage medium provided by the embodiment of the present invention, because the first state identifier is a state identifier of a service interface of a server locally stored by the client, and the second state identifier is a latest state identifier of the service interface, when the client receives the first state identifier sent by the server, because the state identifier received by the client is the same as the state identifier of the service interface locally stored, the client considers that data provided by the service interface is not changed and does not send a request to the service interface, and thus the amount of requests from the client to the service interface can be reduced, thereby reducing impact on the service interface and lowering the probability of unavailability of the service.
Embodiments of the present invention also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the following method steps:
receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface of the server and is locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface;
if yes, the second state identification is sent to the client, and if not, the first state identification is sent to the client, so that the client determines whether to request the service interface according to the received state identification;
and when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface.
Embodiments of the present invention also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the following method steps:
when a specific opportunity is reached, sending a state request containing a first state identifier to a server, wherein the first state identifier is a state identifier of a service interface of the server and locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
receiving a state identifier sent by the server according to a judgment result, wherein the judgment result is as follows: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
judging whether the received state identification is the same as the first state identification or not; and if not, requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface.
According to the program product provided by the embodiment of the invention, because the first state identifier is the state identifier of the service interface of the server locally stored by the client and the second state identifier is the latest state identifier of the service interface, when the client receives the first state identifier sent by the server, the client considers that the data provided by the service interface is not changed and does not send a request to the service interface because the state identifier received by the client is the same as the state identifier of the locally stored service interface, so that the request quantity of the client to the service interface can be reduced, the impact on the service interface is reduced, and the probability of service unavailability is reduced.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device/server/client embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (14)
1. A data transmission method is applied to a server, and comprises the following steps:
receiving a state request which is sent by a client and contains a first state identifier, wherein the first state identifier is a state identifier of a service interface of the server and is locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
judging whether to send a second state identifier to the client, wherein the second state identifier is the latest state identifier of the service interface;
if yes, the second state identification is sent to the client, and if not, the first state identification is sent to the client, so that the client determines whether to request the service interface according to the received state identification;
when a request of the client for the service interface is received, sending data provided by the service interface to the client through the service interface;
the determining whether to send the second state identifier to the client includes:
judging whether to send a second state identification to the client according to a preset probability; or
Judging whether to send a second state identifier to the client according to whether the release time of the client is within a first preset time period; or
And judging whether to send a second state identifier to the client according to the equipment identifier of the equipment where the client is located.
2. The method of claim 1, prior to said determining whether to send the second state identifier to the client, further comprising:
judging whether the second state identifier is the same as the first state identifier or not;
if the state identifiers are the same, the second state identifier is sent to the client;
and if not, executing the step of judging whether to send the second state identification to the client.
3. The method according to any one of claims 1 to 2, wherein the receiving the status request containing the first status identifier sent by the client comprises:
receiving a state request which is sent to a state interface by a client and contains a first state identifier, wherein the state interface stores the state identifiers of all service interfaces of the server;
the sending the second state identifier to the client includes:
and sending the second state identifier stored in the state interface to the client through the state interface.
4. The method according to any of claims 1 to 2, wherein before the determining whether to send the second state identifier to the client, further comprising:
judging whether the current time is within a second preset time period or not;
if not, sending a second state identification to the client;
and if so, executing the step of judging whether to send the second state identification to the client.
5. A data receiving method, applied to a client, the method comprising:
when a specific opportunity is reached, sending a state request containing a first state identifier to a server, wherein the first state identifier is a state identifier of a service interface of the server and locally stored by the client, and the state identifier is an identifier used for representing state information of data provided by the service interface;
receiving a state identifier sent by the server according to a judgment result, wherein the judgment result is as follows: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
judging whether the received state identification is the same as the first state identification or not;
and if not, requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface.
6. The method of claim 5, wherein sending a status request containing the first status identifier to the server comprises:
sending a state request containing a first state identifier to a state interface of a server, wherein the state interface is used for storing the state identifiers of all service interfaces of the server;
correspondingly, the receiving the state identifier sent by the server according to the judgment result includes:
and receiving the state identifier sent by the server through the state interface according to the judgment result.
7. A data transmission apparatus, applied to a server, the apparatus comprising:
a request receiving unit, configured to receive a status request that includes a first status identifier and is sent by a client, where the first status identifier is a status identifier of a service interface of the server and is locally stored by the client, and the status identifier is an identifier used to represent status information of data provided by the service interface;
a sending judgment unit, configured to judge whether to send a second state identifier to the client, where the second state identifier is a latest state identifier of the service interface;
a first identifier sending unit, configured to send the second status identifier to the client when the determination result of the sending determination unit is yes, and send the first status identifier to the client when the determination result of the sending determination unit is no, so that the client determines whether to request the service interface according to the received status identifier;
the data sending unit is used for sending data provided by the service interface to the client through the service interface when a request of the client for the service interface is received;
the sending determination unit is specifically configured to:
judging whether to send a second state identification to the client according to a preset probability; or
Judging whether to send a second state identifier to the client according to whether the release time of the client is within a first preset time period; or
And judging whether to send a second state identifier to the client according to the equipment identifier of the equipment where the client is located.
8. The apparatus of claim 7, further comprising:
a first identifier determining unit configured to determine whether a second status identifier is the same as the first status identifier;
a second identifier sending unit, configured to send the second state identifier to the client when the determination result of the first identifier determining unit is yes;
correspondingly, the sending judging unit is specifically configured to judge whether to send the second state identifier to the client when the judgment result of the first identifier judging unit is negative.
9. The apparatus according to any one of claims 7 to 8, wherein the request receiving unit is specifically configured to receive a status request that is sent by a client to a status interface and that includes a first status identifier, where the status interface stores the status identifiers of the service interfaces of the server;
the first identifier sending unit is specifically configured to send the second status identifier stored in the status interface to the client through the status interface.
10. The apparatus of any one of claims 7 to 8, further comprising:
the time judging unit is used for judging whether the current time is within a second preset time period;
a third identifier sending unit, configured to send a second state identifier to the client when the determination result of the time determination unit is negative;
the sending judging unit is specifically configured to judge whether to send the second state identifier to the client when the judgment result of the time judgment unit is yes.
11. A data receiving apparatus, applied to a client, the apparatus comprising:
a request sending unit, configured to send, when a certain opportunity is reached, a status request including a first status identifier to a server, where the first status identifier is a status identifier of a service interface of the server and locally stored by the client, and the status identifier is an identifier used to represent status information of data provided by the service interface;
an identifier receiving unit, configured to receive a status identifier sent by the server according to a determination result, where the determination result is: the server judges whether a result of sending a second state identification to the client side is obtained, if so, the server sends the second state identification to the client side, if not, the server sends the first state identification to the client side, and the second state identification is the latest state identification of the service interface;
a second identifier determining unit configured to determine whether the received status identifier is the same as the first status identifier;
and the data receiving unit is used for requesting the service interface and receiving the data provided by the service interface and fed back by the server through the service interface when the judgment result of the second identification judging unit is negative.
12. The apparatus according to claim 11, wherein the request sending unit is specifically configured to send a status request including a first status identifier to a status interface of a server when a specific opportunity is reached, where the status interface is configured to store status identifiers of service interfaces of the server;
correspondingly, the identification receiving unit receives the state identification sent by the server through the state interface according to the judgment result.
13. A server is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
the memory is used for storing a computer program;
the processor, when executing the program stored in the memory, is adapted to perform the method steps of any of claims 1-4.
14. The client is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
the memory is used for storing a computer program;
the processor, when executing the program stored in the memory, is adapted to perform the method steps of any of claims 5-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811372142.5A CN109743345B (en) | 2018-11-16 | 2018-11-16 | Data sending and receiving method, device, server and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811372142.5A CN109743345B (en) | 2018-11-16 | 2018-11-16 | Data sending and receiving method, device, server and client |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109743345A CN109743345A (en) | 2019-05-10 |
| CN109743345B true CN109743345B (en) | 2021-08-13 |
Family
ID=66355665
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811372142.5A Active CN109743345B (en) | 2018-11-16 | 2018-11-16 | Data sending and receiving method, device, server and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109743345B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101656652A (en) * | 2008-08-21 | 2010-02-24 | 中国移动通信集团公司 | Content synchronization method, equipment and system for dynamic content delivery |
| CN105100132A (en) * | 2014-04-25 | 2015-11-25 | 北京奇虎科技有限公司 | Terminal device and terminal device identification method and system |
| CN105187475A (en) * | 2015-06-09 | 2015-12-23 | 深圳市金蝶友商电子商务服务有限公司 | Method and system for data synchronization |
| CN107634975A (en) * | 2016-07-18 | 2018-01-26 | 中兴通讯股份有限公司 | A kind of method of data synchronization, equipment and system |
-
2018
- 2018-11-16 CN CN201811372142.5A patent/CN109743345B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101656652A (en) * | 2008-08-21 | 2010-02-24 | 中国移动通信集团公司 | Content synchronization method, equipment and system for dynamic content delivery |
| CN105100132A (en) * | 2014-04-25 | 2015-11-25 | 北京奇虎科技有限公司 | Terminal device and terminal device identification method and system |
| CN105187475A (en) * | 2015-06-09 | 2015-12-23 | 深圳市金蝶友商电子商务服务有限公司 | Method and system for data synchronization |
| CN107634975A (en) * | 2016-07-18 | 2018-01-26 | 中兴通讯股份有限公司 | A kind of method of data synchronization, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109743345A (en) | 2019-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6792510B1 (en) | System and method for updating a cache | |
| US10712915B2 (en) | Information presentation using a client on a terminal | |
| CN108156252B (en) | Data access method and device, server and client | |
| CN110944220B (en) | Video screen projection playing method, device, equipment and system | |
| CN110417910B (en) | Notification message sending method, device, server and storage medium | |
| CN110365745B (en) | Data processing system, method, apparatus, server and computer readable medium | |
| CN111367672A (en) | Data caching method and device, electronic equipment and computer storage medium | |
| CN110730254A (en) | Address allocation method, device, relay equipment and medium | |
| CN111401956A (en) | Advertisement service degradation method, device, server and storage medium | |
| CN115004673A (en) | Message pushing method and device, electronic equipment and computer readable medium | |
| CN105991407B (en) | Message processing method and device and processing server | |
| CN109525654B (en) | Data acquisition and sending method, device, client and server | |
| CN109600254B (en) | Method for generating full-link log and related system | |
| CN111125240B (en) | Distributed transaction realization method and device, electronic equipment and storage medium | |
| CN109743345B (en) | Data sending and receiving method, device, server and client | |
| KR101845195B1 (en) | Multiple Resource Subscriptions Association Method in an M2M system | |
| CN110727895B (en) | Sensitive word sending method and device, electronic equipment and storage medium | |
| CN109922120B (en) | Method and terminal for improving DNS availability | |
| CN107608722B (en) | Application program downloading method and device | |
| CN113835905B (en) | Message queue load balancing method and device, electronic equipment and medium | |
| WO2016118269A1 (en) | Cooperative management of client device cache memory in an http session | |
| CN109962815B (en) | Configuration publishing method, device, server and client device | |
| CN114116219A (en) | Data distribution balancing method and system and electronic equipment | |
| CN113242245A (en) | TCP message flow limiting method, device, server and storage medium | |
| CN113742617A (en) | Cache updating method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |