CN106557262B - Data processing method and device - Google Patents
Data processing method and device Download PDFInfo
- Publication number
- CN106557262B CN106557262B CN201510612732.0A CN201510612732A CN106557262B CN 106557262 B CN106557262 B CN 106557262B CN 201510612732 A CN201510612732 A CN 201510612732A CN 106557262 B CN106557262 B CN 106557262B
- Authority
- CN
- China
- Prior art keywords
- target data
- data
- state
- updated
- client
- 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
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a data processing method and a device, wherein the method comprises the following steps: receiving a target data reading request sent by a client, wherein the target data reading request carries a data identifier; reading the target data according to the data identification and generating a state identification for identifying the update state of the target data; sending the target data carrying the state identification to a client; receiving updated target data which is sent by a client and obtained after the target data is updated, wherein the updated target data carries a state identifier; judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data at present; and when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data at present, storing the updated target data and updating the state identifier. By adopting the embodiment of the invention, the reliability of data processing can be improved.
Description
Technical Field
The present invention relates to the field of computer application technologies, and in particular, to a data processing method and apparatus.
Background
At present, a cache is an essential important component of any node device, and in the face of high concurrent reading and writing of mass data, a cache system can greatly improve the data reading capacity of the system. But in the high concurrent read-write state, if the modification is frequent for the same data, the reliability of the data will be reduced.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a data processing method and apparatus, which can improve the reliability of data processing.
In order to solve the above technical problem, an embodiment of the present invention provides a data processing method, including:
receiving a target data reading request sent by a client, wherein the target data reading request carries a data identifier;
reading the target data according to the data identification, and generating a state identification for identifying the update state of the target data;
sending the target data carrying the state identification to the client;
receiving updated target data which is sent by the client and obtained after the target data is updated, wherein the updated target data carries the state identification;
judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data at present;
and when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently, storing the updated target data and updating the state identifier.
Correspondingly, an embodiment of the present invention further provides a data processing apparatus, including:
the device comprises a reading request receiving unit, a reading request sending unit and a processing unit, wherein the reading request receiving unit is used for receiving a target data reading request sent by a client, and the target data reading request carries a data identifier;
the first data reading unit is used for reading the target data according to the data identification and generating a state identification used for identifying the update state of the target data;
the first data sending unit is used for sending the target data carrying the state identifier to the client;
a second data receiving unit, configured to receive updated target data sent by the client and obtained after the target data is updated, where the updated target data carries the state identifier;
a judging unit, configured to judge whether a state identifier carried by the updated target data is the same as a state identifier currently used for identifying an update state of the target data;
and the second data storage unit is used for storing the updated target data and updating the state identifier when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently.
By implementing the embodiment of the invention, the target data reading request sent by the client is received, the target data is read according to the data identifier carried by the target data reading request, the state identifier for identifying the update state of the target data is generated, the target data carrying the state identifier is sent to the client, the updated target data obtained after the target data is updated and sent by the client is received, and when the state identifier carried by the updated target data is the same as the state identifier for identifying the update state of the target data at present, the updated target data is stored and the state identifier is updated, so that the reliability of data processing can be improved.
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, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a data processing method provided in an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a data processing method according to another embodiment of the present invention;
FIG. 3 is a flow chart illustrating a data processing method according to another embodiment of the present invention;
fig. 4 is a schematic structural diagram of a data processing apparatus provided in an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of the first data reading unit of FIG. 4 according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a node device provided in an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the conventional data processing method, in a large concurrent read-write state, a plurality of clients read data in a cache file in the same time period and correspondingly update the data, which causes data processing abnormity, cannot synchronize the data in the cache file and the data in a persistent file, and reduces the reliability of data processing.
The embodiment of the invention provides a data processing method, which comprises the steps of receiving a target data reading request sent by a client, reading target data according to a data identifier carried by the target data reading request, generating a state identifier for identifying the update state of the target data, sending the target data carrying the state identifier to the client, receiving updated target data obtained after the target data is updated and sent by the client, storing the updated target data when the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, updating the state identifier, and improving the reliability of data processing.
Embodiments of the present invention refer to target data as images, text, audio, or video. The data identifier may be used to identify the target data, such as a data name, a storage path, or a data amount. The state identifier may be used to identify an update state of the target data, such as a data version number or a timestamp. The updating of the state identifier in the embodiment of the present invention may be: add one to the data version number, or convert the timestamp to a timestamp indicating the current system time, etc. And are not particularly limited by the embodiments of the present invention.
The data processing method can be operated in node equipment such as a Personal Computer (PC), a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet Computer, or wearable smart device.
Referring to fig. 1, fig. 1 is a schematic flow chart of a data processing method in an embodiment of the present invention, where the data processing method in the embodiment of the present invention includes:
s101, receiving a target data reading request sent by a client, wherein the target data reading request carries a data identifier.
The node device may receive a target data read request sent by a client. The target data reading request may carry a data identifier, for example, the data identifier may be one or more of a data name, a storage path, or a data amount. The client may be a web browser or an email client, etc. The node device may act as a server, such as an email server or the like. In a specific implementation, the node device may establish a communication connection with the client, and further receive a target data reading request sent by the client through the established communication connection with the client. When the node device and the client fail to connect, connection failure information may be sent to the client to indicate that the establishment of the communication connection with the node device has failed.
In an optional embodiment, the number of the clients may be at least one, and the node device may receive target data reading requests sent by the at least one client, where each target data reading request carries a data identifier. In a specific implementation, the node device may receive a target data reading request sent by at least one client through a plurality of read-write agent modules, for example, the node device receives a target data reading request sent by a first client through a first read-write agent module, receives a target data reading request sent by a second client through a second read-write agent module, and so on. According to the embodiment of the invention, the target data reading request sent by at least one client is received by the plurality of reading and writing agent modules, so that the effectiveness of data processing can be improved.
S102, reading the target data according to the data identification, and generating a state identification for identifying the update state of the target data.
The node device may read the target data according to the data identification and generate a state identification for identifying an update state of the target data. The state identification may be a data version number or a timestamp, etc. In a specific implementation, after the node device reads the target data, a redis command watch a may be executed, where a is the target data, and then a state identifier for identifying an update state of the target data is generated.
In an optional embodiment, after receiving the target data read request, the node device may determine whether the cache file includes the target data, and load the target data from the persistent file according to the data identifier when the cache file does not include the target data.
S103, sending the target data carrying the state identification to the client.
After the node device generates the state identifier, the target data carrying the state identifier may be sent to the client. In a specific implementation, after the node device sends the target data to the client, the client may update the target data, for example, modify, add, or delete information in the target data.
And S104, receiving updated target data which is obtained after the target data is updated and sent by the client, wherein the updated target data carries the state identifier.
The node device may receive updated target data sent by the client and obtained by updating the target data, where the updated target data carries the state identifier. The state identifier sent by the client and received by the node device is the same as the state identifier sent by the node device to the client.
S105, judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently.
After receiving the updated target data sent by the client, the node device may determine whether the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, and further perform step S106 when the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data; when the state identifier carried by the updated target data is different from the state identifier currently used for identifying the update state of the target data, the node device may delete the updated target data.
For example, in the process of updating the target data by the client, if the target data stored by the node device has been updated by other clients, the node device updates the state identifier for identifying the update state of the target data, and the client determines that the state identifier carried by the sent updated target data is different from the state identifier currently used for identifying the update state of the target data, thereby deleting the updated target data sent by the client. For another example, in the process of updating the target data by the client, the target data stored by the node device is not updated by other clients, the state identifier currently used for identifying the update state of the target data remains unchanged, and the client determines that the state identifier carried by the sent updated target data is the same as the state identifier currently used for identifying the update state of the target data, so as to store the updated target data sent by the client and update the state identifier.
Further optionally, after deleting the updated target data, the node device may send an update failure message to the client, so that the client resends the target data reading request, and then the node device executes steps S101 to S105.
S106, storing the updated target data and updating the state identification.
When the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, the node device may store the updated target data and update the state identifier. When the state identifier is a data version number, the updating of the state identifier by the node device may be: adding one to the data version number; when the status identifier is the timestamp, the node device may update the status identifier by: and acquiring a timestamp corresponding to the current system time, and taking the timestamp corresponding to the current system time as an updated state identifier.
In a specific implementation, when the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, the node device may perform fragment caching on the updated target data. For example, the node device may set a plurality of cache files, and store the updated target data into the plurality of cache files based on a consistent hash algorithm, thereby implementing fragmented cache data. The embodiment of the invention can improve the effectiveness of data processing.
In an optional embodiment, the node device stores updated target data, which may specifically be storing the updated target data in a cache file, further, after the node device stores the updated target data in the cache file, the updated target data may be stored in a persistent file, where the cache file may be a memory, a RAM (random access memory), a ROM (read-only memory), or the like, the persistent file may be a disk, an XM L data file, or the like, a state of data in the cache file is an instant state, and a state of data in the persistent file is a persistent state.
In the embodiment of the invention, a target data reading request sent by a client is received, target data is read according to a data identifier carried by the target data reading request, a state identifier for identifying the update state of the target data is generated, the target data carrying the state identifier is sent to the client, the updated target data obtained after the target data is updated and sent by the client is received, and when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data at present, the updated target data is stored and the state identifier is updated, so that the reliability of data processing can be improved.
Referring to fig. 2, fig. 2 is a schematic flow chart of a data processing method according to another embodiment of the present invention, where the data processing method according to the embodiment of the present invention includes:
s201, receiving a target data reading request sent by a client, wherein the target data reading request carries a data identifier.
The node device may receive a target data reading request sent by a client, where the target data reading request may carry a data identifier. In a specific implementation, the node device may establish a communication connection with the client, and further receive a target data reading request sent by the client through the established communication connection with the client. When the node device and the client fail to connect, connection failure information may be sent to the client to indicate that the establishment of the communication connection with the node device has failed.
S202, judging whether the cache file comprises the target data or not.
After receiving the target data reading request, the client can judge whether the cache file comprises the target data according to the data identifier carried by the target data reading request, and when the cache file comprises the target data, the client reads the target data from the cache file; when the target data is not included in the cache file, step S203 is further performed.
S203, loading the target data from the persistent file according to the data identification.
When the target data does not exist in the cache file, the node device may load the target data from the persistent file according to the data identifier.
S204, generating a state identifier for identifying the update state of the target data.
In a specific implementation, after the node device loads the target data, a redis command watch a may be executed, where a is the target data, and then a state identifier for identifying an update state of the target data is generated.
And S205, sending the target data carrying the state identifier to the client.
And S206, receiving updated target data which is obtained by updating the target data and is sent by the client, wherein the updated target data carries the state identifier.
S207, judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently.
S208, deleting the updated target data.
S209, sending an update failure message to the client, so that the client resends the target data read request.
In the embodiment of the invention, a target data reading request sent by a client is received, when the cache file does not contain target data, the target data is loaded from a persistent file according to a data identifier carried by the target data reading request, a state identifier for identifying the update state of the target data is generated, the target data carrying the state identifier is sent to the client, the updated target data obtained after the target data is updated and sent by the client is received, when the state identifier carried by the updated target data is different from the state identifier currently used for identifying the update state of the target data, the updated target data is deleted, and an update failure message is sent to the client, so that the client resends the target data reading request, and the reliability of data processing can be improved.
Referring to fig. 3, fig. 3 is a schematic flow chart of a data processing method in another embodiment of the present invention, where the data processing method in the embodiment of the present invention includes:
s301, the first client sends a target data reading request to the node device, and the target data reading request carries a data identifier.
S302, the second client sends a target data reading request to the node equipment, and the target data reading request carries a data identifier.
And S303, the node equipment reads the target data according to the data identification and generates a state identification for identifying the update state of the target data.
S304, the node equipment sends the target data carrying the state identification to the first client.
S305, the node equipment sends the target data carrying the state identification to a second client.
S306, the first client updates the target data to obtain first target data, and the first target data carries the state identifier.
S307, the first client sends the first target data to the node device.
S308, the node equipment determines that the state identifier carried by the first target data is the same as the state identifier used for identifying the update state of the target data currently.
S309, the node device stores the first target data and updates the state identifier.
And S310, the second client updates the target data to obtain second target data, and the second target data carries the state identifier.
And S311, the second client sends the second target data to the node equipment.
S312, the node device determines that the state identifier carried by the second target data is different from the state identifier currently used for identifying the update state of the target data.
S313, the node apparatus deletes the second target data.
In the embodiment of the invention, a node device reads target data according to a data identifier carried by a target data reading request, generates a state identifier for identifying the update state of the target data, sends the target data carrying the state identifier to a first client and a second client, the first client sends first target data obtained by updating the target data to the node device, the node device determines that the state identifier carried by the first target data is the same as the state identifier currently used for identifying the update state of the target data, the node device stores the first target data and updates the state identifier, the second client sends second target data obtained by updating the target data to the node device, the node device determines that the state identifier carried by the second target data is not the same as the state identifier currently used for identifying the update state of the target data, and then delete the second target data, can improve the reliability of data handling.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a data processing apparatus provided in an embodiment of the present invention, where the data processing apparatus in the embodiment of the present invention may include a node device such as a personal computer, a smart phone, a tablet computer, or a wearable smart device, and as shown in the figure, the data processing apparatus in the embodiment of the present invention may at least include a read request receiving unit 401, a first data reading unit 402, a first data sending unit 403, a second data receiving unit 404, a determining unit 405, and a second data storing unit 406, where:
a read request receiving unit 401, configured to receive a target data read request sent by a client, where the target data read request carries a data identifier.
A first data reading unit 402, configured to read the target data according to the data identifier, and generate a state identifier for identifying an update state of the target data.
A first data sending unit 403, configured to send the target data carrying the status identifier to the client.
The second data receiving unit 404 is configured to receive updated target data, which is sent by the client and obtained after the target data is updated, where the updated target data carries the state identifier.
The determining unit 405 is configured to determine whether the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data.
A second data storage unit 406, configured to store the updated target data and update the state identifier when the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data.
In an optional embodiment, the data processing apparatus in the embodiment of the present invention may further include:
a deleting unit 407, configured to delete the updated target data when the state identifier carried by the updated target data is different from the state identifier currently used to identify the update state of the target data.
Further optionally, the data processing apparatus in the embodiment of the present invention may further include:
a message sending unit 408, configured to send an update failure message to the client after the deleting unit 407 deletes the updated target data, so that the client resends the target data reading request.
In an alternative embodiment, the second data storage unit 406 is configured to store the updated target data in a cache file.
Further, the second data storage unit 406 is also used for storing the updated target data into the persistent file.
In an alternative embodiment, the first data reading unit 402 in the embodiment of the present invention may be as shown in fig. 5, further including:
the first data determining module 501 is configured to determine whether the cache file includes target data.
The first data loading module 502 is configured to load the target data from the persistent file according to the data identifier when the target data is not included in the cache file.
In the embodiment of the present invention, a reading request receiving unit 401 receives a target data reading request sent by a client, a first data reading unit 402 reads target data according to a data identifier carried in the target data reading request, and generates a state identifier for identifying an update state of the target data, a first data sending unit 403 sends the target data carrying the state identifier to the client, a second data receiving unit 404 receives updated target data obtained after updating the target data sent by the client, and when a judging unit 405 judges that the state identifier carried in the updated target data is the same as the state identifier currently used for identifying the update state of the target data, a second data storing unit 406 stores the updated target data, and updates the state identifier, which can improve reliability of data processing.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a node device according to an embodiment of the present invention, where the node device according to the embodiment of the present invention may be used to implement the method implemented by the embodiments of the present invention shown in fig. 1 to fig. 3, for convenience of description, only the part related to the embodiments of the present invention is shown, and details of the specific technology are not disclosed, please refer to the embodiments of the present invention shown in fig. 1 to fig. 3.
As shown in fig. 6, the node apparatus includes: at least one processor 601, e.g., a CPU, at least one network interface 603, memory 604, at least one communication bus 602. Wherein a communication bus 602 is used to enable the connection communication between these components. Memory 604 may comprise high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory. The memory 604 may optionally include at least one storage device located remotely from the processor 601. The processor 601 may incorporate the data processing apparatus shown in fig. 4. A set of program code is stored in memory 604 and processor 601 calls the program code stored in memory 604 for performing the following:
a target data reading request sent by a client is received through the network interface 603, and the target data reading request carries a data identifier.
And reading the target data according to the data identification, and generating a state identification for identifying the update state of the target data.
And sending the target data carrying the state identifier to the client through the network interface 603.
And receiving updated target data which is obtained by updating the target data and sent by the client through the network interface 603, wherein the updated target data carries a state identifier.
And judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently.
And when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data at present, storing the updated target data and updating the state identifier.
In an optional embodiment, after the processor 601 determines whether the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, the following operations may also be performed:
and when the state identifier carried by the updated target data is different from the state identifier used for identifying the update state of the target data currently, deleting the updated target data.
Further optionally, after the processor 601 deletes the updated target data, the following operations may be further performed:
an update failure message is sent to the client through the network interface 603 to cause the client to resend the target data read request.
In an alternative embodiment, the processor 601 stores the updated target data, which may specifically be:
and storing the updated target data into a cache file.
Further, after the processor 601 stores the updated target data in the cache file, the following operations may be further performed:
storing the updated target data into a persistent file.
In an alternative embodiment, the processor 601 reads the target data according to the data identifier, which may specifically be:
and judging whether the cache file comprises target data or not.
And when the target data is not included in the cache file, loading the target data from the persistent file according to the data identification.
Specifically, the node device described in the embodiment of the present invention may be used to implement part or all of the processes in the method embodiments described in conjunction with fig. 1 to fig. 3 of the present invention.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (12)
1. A data processing method, comprising:
receiving a target data reading request sent by at least one client, wherein the target data reading request carries a data identifier;
reading the target data according to the data identification, and generating a state identification for identifying the update state of the target data;
sending the target data carrying the state identification to each client;
receiving updated target data which is sent by each client and obtained after the target data is updated, wherein the updated target data carries the state identification;
for each updated target data, judging whether the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently;
and when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently, storing the updated target data and updating the state identifier.
2. The method according to claim 1, wherein after determining whether the state identifier carried by the updated target data is the same as the state identifier currently used for identifying the update state of the target data, the method further comprises:
and when the state identifier carried by the updated target data is different from the state identifier used for identifying the update state of the target data currently, deleting the updated target data.
3. The method of claim 2, wherein after deleting the updated target data, further comprising:
and sending an update failure message to the client so that the client resends the target data reading request.
4. The method of claim 1, wherein storing the updated target data comprises:
storing the updated target data into a cache file;
after storing the updated target data into the cache file, the method further includes:
storing the updated target data in a persistent file.
5. The method of claim 1, wherein reading the target data according to the data identifier comprises:
judging whether the cache file comprises the target data or not;
and when the target data is not included in the cache file, loading the target data from a persistent file according to the data identifier.
6. A node apparatus, comprising:
the device comprises a reading request receiving unit, a reading request receiving unit and a processing unit, wherein the reading request receiving unit is used for receiving a target data reading request sent by at least one client, and the target data reading request carries a data identifier;
the first data reading unit is used for reading the target data according to the data identification and generating a state identification used for identifying the update state of the target data;
the first data sending unit is used for sending the target data carrying the state identification to each client;
a second data receiving unit, configured to receive updated target data obtained after the target data is updated and sent by each client, where the updated target data carries the state identifier;
a determining unit, configured to determine, for each updated target data, whether a state identifier carried by the updated target data is the same as a state identifier currently used for identifying an update state of the target data;
and the second data storage unit is used for storing the updated target data and updating the state identifier when the state identifier carried by the updated target data is the same as the state identifier used for identifying the update state of the target data currently.
7. The node device of claim 6, further comprising:
and the deleting unit is used for deleting the updated target data when the state identifier carried by the updated target data is different from the state identifier used for identifying the update state of the target data currently.
8. The node device of claim 7, wherein the node device further comprises:
and the message sending unit is used for sending an update failure message to the client after the deleting unit deletes the updated target data, so that the client resends the target data reading request.
9. The node apparatus of claim 6,
the second data storage unit is used for storing the updated target data into a cache file;
the second data storage unit is further used for storing the updated target data into a persistent file.
10. The node device according to claim 6, wherein the first data reading unit includes:
the first data judgment module is used for judging whether the cache file comprises the target data or not;
and the first data loading module is used for loading the target data from the persistent file according to the data identifier when the target data is not included in the cache file.
11. A node apparatus, characterized in that the apparatus comprises:
a memory for storing a computer program;
a processor for invoking the computer program stored in the memory for performing the data processing method of any of claims 1 to 5.
12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the data processing method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510612732.0A CN106557262B (en) | 2015-09-23 | 2015-09-23 | Data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510612732.0A CN106557262B (en) | 2015-09-23 | 2015-09-23 | Data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106557262A CN106557262A (en) | 2017-04-05 |
| CN106557262B true CN106557262B (en) | 2020-07-14 |
Family
ID=58413497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510612732.0A Active CN106557262B (en) | 2015-09-23 | 2015-09-23 | Data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106557262B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108011949B (en) * | 2017-11-30 | 2021-03-09 | 百度在线网络技术（北京）有限公司 | Method and apparatus for acquiring data |
| CN108196515A (en) * | 2017-12-21 | 2018-06-22 | 中国电子信息产业集团有限公司第六研究所 | Cross-platform real-time data processing method and device |
| CN109002535B (en) * | 2018-07-18 | 2023-03-24 | 腾讯科技（深圳）有限公司 | Data updating method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101540726A (en) * | 2009-04-27 | 2009-09-23 | 华为技术有限公司 | Method, client, server and system of synchronous data |
| CN103294675A (en) * | 2012-02-23 | 2013-09-11 | 上海盛霄云计算技术有限公司 | Method and device for updating data in distributed storage system |
| CN103747072A (en) * | 2013-12-30 | 2014-04-23 | 乐视网信息技术（北京）股份有限公司 | Data reading and writing method and application server |
| WO2015074467A1 (en) * | 2013-11-25 | 2015-05-28 | 腾讯科技（深圳）有限公司 | Data update method, apparatus, and system and storage medium |
-
2015
- 2015-09-23 CN CN201510612732.0A patent/CN106557262B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101540726A (en) * | 2009-04-27 | 2009-09-23 | 华为技术有限公司 | Method, client, server and system of synchronous data |
| CN103294675A (en) * | 2012-02-23 | 2013-09-11 | 上海盛霄云计算技术有限公司 | Method and device for updating data in distributed storage system |
| WO2015074467A1 (en) * | 2013-11-25 | 2015-05-28 | 腾讯科技（深圳）有限公司 | Data update method, apparatus, and system and storage medium |
| CN103747072A (en) * | 2013-12-30 | 2014-04-23 | 乐视网信息技术（北京）股份有限公司 | Data reading and writing method and application server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106557262A (en) | 2017-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107643880B (en) | File data migration method and device based on distributed file system | |
| KR101766790B1 (en) | Method and computing apparatus for maniging main memory database | |
| US8943149B2 (en) | Sender motivated optimization of URI rendering in instant messaging | |
| US20150331902A1 (en) | Distributed Storage Object Delete | |
| CN109981715B (en) | Session management method and device | |
| CN108874825B (en) | Abnormal data verification method and device | |
| CN110019873B (en) | Face data processing method, device and equipment | |
| CN106557262B (en) | Data processing method and device | |
| EP3506599B1 (en) | Method for synchronizing contact information, apparatus and medium | |
| CN102752371A (en) | Method for achieving splash on client side and client side | |
| CN111338834B (en) | Data storage method and device | |
| CN114637611A (en) | Information processing method and device based on message queue and computer equipment | |
| CN108133026B (en) | Multi-data processing method, system and storage medium | |
| CN107357808B (en) | Data management method, device and equipment | |
| CN111327680B (en) | Authentication data synchronization method, device, system, computer equipment and storage medium | |
| CN108241616B (en) | Message pushing method and device | |
| KR20170106626A (en) | Method and computing apparatus for maniging main memory database | |
| CN105610596B (en) | Resource directory management method and network terminal | |
| CN111159298A (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN111930696B (en) | File transmission processing method and system based on small program | |
| CN114253924A (en) | Synchronization method, synchronization equipment and storage medium | |
| CN114285657A (en) | Firewall security policy change verification method and device | |
| CN114186976A (en) | Workflow transfer method and device, computer equipment and storage medium | |
| CN107295179A (en) | The method and apparatus that a kind of short message is shown | |
| CN107704557B (en) | Processing method and device for operating mutually exclusive data, computer equipment and storage medium |
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 |