CN102541941A - Version management control method for multiple parties to co-operate file - Google Patents
Version management control method for multiple parties to co-operate file Download PDFInfo
- Publication number
- CN102541941A CN102541941A CN2010106192986A CN201010619298A CN102541941A CN 102541941 A CN102541941 A CN 102541941A CN 2010106192986 A CN2010106192986 A CN 2010106192986A CN 201010619298 A CN201010619298 A CN 201010619298A CN 102541941 A CN102541941 A CN 102541941A
- Authority
- CN
- China
- Prior art keywords
- file
- server
- working area
- area
- version
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 230000004048 modification Effects 0.000 claims abstract description 11
- 238000012986 modification Methods 0.000 claims abstract description 11
- 230000002452 interceptive effect Effects 0.000 claims description 22
- 230000003993 interaction Effects 0.000 abstract description 9
- 230000006872 improvement Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a version management control method for multiple parties to co-operate a file. A work area, a standard area and an interaction area are arranged at a client side for each user, wherein local modifications to the file by the user are stored in the work area, a file newly uploaded to a server by the user is stored in the standard area, and the file downloaded from the server is stored in the interaction area. When the file is updated on the server, whether the version of the file in the work area is lower than the version of the file in the server is firstly judged; and under the circumstance that the version of the file in the work area is lower than the version of the file in the server, the consistency between the file in the standard area and the file in the work area is compared; if the file in the standard area is not consistent with the file in the work area, the file in the standard area is downloaded to the interaction area from the server; the downloaded file is modified and is combined with the file in the work area; and then the combined area is stored in the work area. Thereby, when the local file and the file in the server are both modified, the local file is prevented from being directly covered by the file in the server, so modification conflicts between the local file and the file in the server are prevented from the angle of local file protection.
Description
Technical Field
The invention relates to a file version control technology
Background
Many engineering documents, scientific articles, academic reports, and software source codes are often written and modified by multiple authors (users) at the same time, and long-time repeated communication coordination is often required to effectively and error-free perform "cooperative" operations. And the required communication costs increase dramatically with the number of people modified at the same time.
In order to resolve the "conflict" caused by such "cooperative" operation, the following solutions are commonly used:
1. the exclusive mode is adopted, namely, the file is stored on a publicly accessible server, and when a certain user operates the file (object), the server performs locking on the file. By "locked" is meant that the same file is only allowed to be modified exclusively by one user at a time. Therefore, the system can be edited and modified by one user at a time, thereby avoiding 'cooperation' operation and generating no conflict. However, such a solution gives up collaboration altogether, resulting in a waste of other productivity. And after "locking" when the user leaves, other users cannot efficiently update and modify.
2. Third party version control tools are introduced, such as SVN, CVS, GIT, etc. These version control systems are introduced to record and track any changes that occur to all files within a system, and if multiple users modify a file at the same time, the version control systems attempt to automatically merge according to some algorithm. Only when two or more users modify the same line of the file at the same time, the version control system does not automatically merge the modifications, but rather prompts a "conflict" that prompts the user himself to manually resolve the "conflict". This solution requires the user to install the corresponding client and the server to install the corresponding server. This is a burden for some projects. And it is sometimes difficult to perfectly blend with existing projects to install third party version control tools.
3. The collision control is performed by a common protocol. This method is to stipulate a specification in advance among all users, allocate respective operation objects so that the operation objects do not overlap with each other as much as possible, and then check after a short period of time. This method has a very significant drawback, i.e. it does not have a strong constraining effect. Are generally used only rarely, and are used only in a few specific cases.
Disclosure of Invention
The invention mainly solves the technical problem of providing a version management control method of a multi-party cooperative operation file, so that a multi-party user can effectively operate the same file without errors, and various conflicts caused by the multi-party cooperative operation of the same file are effectively avoided.
In order to solve the above technical problem, the present invention provides a version management control method for a multi-party cooperative file, comprising the following steps:
setting a working area, a standard area and an interactive area for each user at a client, wherein the working area stores the local modification of the file by the user, the standard area stores the file which is uploaded to a server by the user latest, and the interactive area stores the file downloaded from the server;
when updating the file from the server, if the file exists in the working area and the version of the file in the working area is lower than that of the file in the server, comparing the consistency of the file in the standard area and the file in the working area, if the file is not consistent, downloading the file from the server to the interactive area, modifying and combining the downloaded file and the file in the working area, saving the combined file to the working area, and updating the version of the file in the working area.
As an improvement of the above technical solution, the method further comprises the steps of:
if the file in the standard area is consistent with the file in the working area, downloading the file from the server to the working area, and updating the file version in the working area; or,
and if the file in the standard area is consistent with the file in the working area, downloading the file from the server to the interactive area, copying the downloaded file to the working area, and updating the file version in the working area.
As an improvement of the above technical solution, the method further comprises the steps of:
when a file is updated from the server, if the file already exists in the working area and the version of the file in the working area is not lower than the version of the file in the server, the update is terminated.
As an improvement of the above technical solution, the method further comprises the steps of:
when updating a file from a server, if the file does not exist in a working area, downloading the file from the server to the working area, and updating the file version in the working area; or downloading the file from the server to the interactive area, copying the downloaded file to the working area, and updating the file version in the working area.
As an improvement of the above technical solution, after the file in the working area is updated, the method further comprises the following steps: and saving the updated file and the file version in the working area to the standard area.
As an improvement of the above technical solution, the method further comprises the steps of:
when the user submits the file in the working area to the server, if the file exists in the server and the version number of the file in the server is higher than that of the file in the working area, the submitting operation is stopped, and the file is updated.
As an improvement of the above technical solution, in the step of suspending the submitting operation and updating the file, the file is directly downloaded from the server to the interactive area, the downloaded file is modified and merged with the file in the working area, the merged file is saved in the working area, and the version of the file in the working area is updated.
And after the file is updated, the file is submitted again.
As an improvement of the above technical solution, the method further comprises the steps of:
when a user submits a file in a working area to a server, if the file does not exist in the server, the file in the working area is directly uploaded to the server, the version number of the uploaded file is updated, and the uploaded file and the version number thereof are stored in a local standard area.
As an improvement of the above technical solution, the method further comprises the steps of:
when a user submits a file in a working area to a server, if the file exists in the server, the version number of the file in the server is compared with the version number of the file in the working area, if the version number of the file in the server is not higher than the version number of the file in the working area, the file in the working area is directly uploaded to the server, the version number of the uploaded file is updated, and the uploaded file and the version number thereof are stored in a local standard area.
Compared with the prior art, the implementation mode of the invention has the main differences and the effects that: the method comprises the steps that a working area, a standard area and an interaction area are set for each user at a client, local modification of a file by the user is stored in the working area, the file which is uploaded to a server by the user latest is stored in the standard area, and the file downloaded from the server is stored in the interaction area. When updating a file from a server, firstly judging whether the file exists in a working area and whether the version of the file in the working area is lower than that of the file in the server, comparing the consistency of the file in a standard area and the file in the working area under the condition that the file exists in the working area and the version of the file is lower than that in the server, downloading the file from the server to an interactive area if the file does not accord with the version of the file in the working area, modifying and merging the downloaded file and the file in the working area, saving the merged file to the working area, and updating the version of the file in the working area. Therefore, when the local file and the server file are modified, the local file is directly covered by the file in the server, and modification conflict between the local file and the file on the server is avoided from the perspective of protecting the local file.
When the user submits the file in the working area to the server, if the file exists in the server and the version number of the file in the server is higher than that of the file in the working area, the submitting operation is stopped, and the file is updated. The update can be a technical combination of the file downloaded by the server and the modified file in the working area. Therefore, when the local file and the server file are modified, the file in the server is directly covered by the local file, and modification conflict between the local file and the file on the server is avoided from the perspective of protecting the file on the server.
Drawings
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
FIG. 1 is a flowchart of a file update method in a version management control method for a multi-party interoperation file according to a preferred embodiment of the present invention;
FIG. 2 is a flowchart of a file submission method in the version management control method for multi-party collaborative operation files according to a preferred embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The invention relates to a version management control method of a multi-party cooperative operation file. The file herein refers not only to a text file but also includes other objects on the server. In this embodiment, a work area, a standard area, and an interactive area are set for each user at the client. The files (including various data objects) stored in the working area can be directly modified, compiled and the like by a user, and are working spaces of the user; storing a file which is uploaded to a server by a client locally and latest in the standard area; the interactive area stores the files downloaded from the server to the local, and the files downloaded from the server to the local are generally required to be placed in the working area for the user to operate, so the interactive area is only a temporary area. And storing a configuration file in the standard area of each client to record file related information in the standard area, wherein the file related information comprises a version number, a latest uploaded user name, time and a message digest MD5 value of the file. The concrete structure is as follows:
Struct{Version，Username，Time，MD5，...}；
message Digest Algorithm MD5 (the fifth version of the chinese name Message Digest Algorithm) is a widely used hash function in the field of computer security to provide integrity protection for messages.
The client and the server mainly perform file Update (Update) and file Commit (Commit) operations. Updating, namely downloading the latest version of the file on the server to the local, and ensuring the identity of the local and the file on the server; and submission refers to uploading a local file to a server (usually, after the file is locally modified, submission is needed). Generally, before a user locally modifies a file and submits the modified file to a server, the user needs to first determine whether the version of the file on the server changes, and if the version of the file changes, it indicates that other users modify the file, need to update the file, and upload the file again after updating the file. As can be seen, the commit operation must rely on the update operation, both of which are interrelated.
First, a file update flow is described, as shown in fig. 1.
In step 101, checking whether a corresponding file exists in a local working area of a client, and if not, directly entering step 102; if so, step 103 is entered.
In step 102, the file is directly downloaded from the server to the working area of the local client, and the local version number is modified, so that the local version number of the file is the same as that of the server, the update of the file is completed, and the step 107 is entered. Or, in order to make the downloading more secure and standardized, the file may be downloaded from the server to the interactive area of the local client, the file is updated, and then the file is copied from the interactive area to the working area, so that the user can perform operations such as modification and compilation, and then the process proceeds to step 107.
103, comparing the version number of the file in the local working area with the version number of the file on the server, if the version number of the file on the server is lower than or equal to the version number of the file in the local working area (generally, the situation of lower than the version number is rarely occurred, and the situation can be ignored), indicating that the file stored locally is the current latest version, and the process is ended without updating; if the file version number on the server is higher than the file version number in the local standard area, step 104 is entered.
Step 104, respectively calculating MD5 of the file in the local working area and the standard area of the client, if MD5 is the same, it indicates that the file in the local working area has not been modified after the file was uploaded for the previous time, entering step 102, directly downloading the file on the server to the local working area, covering the original file in the working area, modifying the local version number to make the local version number of the file the same as that on the server, completing the update of the file, and then entering step 107; if the calculated MD5 is not the same, it indicates that the user modified the file in the local workspace after the previous upload of the file, and then step 105 is entered.
In step 105, the file on the server is downloaded to the local interactive area, and then step 106 is entered.
In step 106, the file in the interactive area and the file in the working area are modified and merged by using a local merging tool, and the merged file is stored in the local working area and the local version number is modified, so that the local version number of the file is the same as that of the server. Therefore, when the local file and the server file are modified, the local file is directly covered by the file in the server, and modification conflict between the local file and the file on the server is avoided from the perspective of protecting the local file. At this point, the entire update operation is complete. Step 107 is then entered. The local merging tool may be professional comparison merging software beyond company, open source free software WinMerge, diff-merge software of google, or the like, and may also develop a corresponding merging tool by itself.
In step 107, the updated file and file version in the working area are saved to the standard area.
In this embodiment, after determining that the version number of the file on the server is higher than the version number of the file in the local standard region in step 103, the file on the server may also be directly downloaded to the local interaction region, and then MD5 of the file in the local working region and the standard region is calculated, and if MD5 is the same, the file in the local interaction region is directly copied to the working region to cover the original file in the working region; if the calculated MD5 is different, modifying and merging the file in the interactive area and the file in the working area by using a local merging tool, storing the merged file in the local working area, and modifying the local version number so that the local version number of the file is the same as that on the server.
In the present embodiment, only one profile is stored in the standard area, and information such as the version number and MD5 value of the file in the standard area is recorded. After each update, the version number of the file in the standard area and the version number of the file in the working area are updated synchronously, so in the above process, the version number of the file in the current working area can be directly obtained from the configuration file of the standard area.
After the user modifies the file, the processed file needs to be submitted to the server, and the whole process of the submit (Commit) operation will be described as follows:
in step 201, checking whether the file exists on the server, if not, entering step 202 to directly upload the local work area file to the server, updating the version number of the uploaded file, and then entering step 203; if so, go to step 204.
In step 203, the uploaded file is copied to the local interactive area, and a new version number of the uploaded file and file configuration information such as MD5 are maintained.
In step 204, comparing the version numbers of the file in the server and the local working area, if the version number of the file on the server is equal to or lower than the version number of the file in the local working area, entering step 202, directly uploading the file in the local working area to the server, updating the version number of the uploaded file, and then entering step 203; if the file version number on the server is higher than the file version number in the local working area, go to step 205.
In step 205, uploading is prohibited, and the user is prompted to perform the update operation of the file first.
After the user selects the update operation, the update flow shown in fig. 1 may be entered. Or, in order to simplify the operation, directly jumping to step 106, downloading the file on the server into the local interaction area, modifying and merging the file in the interaction area and the file in the working area by using a local merging tool, storing the merged file in the local working area, and modifying the local version number to make the local version number of the file the same as that on the server. Therefore, when the local file and the server file are modified, the file in the server is directly covered by the local file, and modification conflict between the local file and the file on the server is avoided from the perspective of protecting the file on the server.
After the file is updated, the user may resubmit the updated file.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
Claims (11)
1. A version management control method for a multi-party cooperative operation file is characterized by comprising the following steps:
setting a working area, a standard area and an interactive area for each user at a client, wherein the working area stores the local modification of the file by the user, the standard area stores the file which is uploaded to a server by the user latest, and the interactive area stores the file downloaded from the server;
when updating the file from the server, if the file exists in the working area and the version of the file in the working area is lower than that of the file in the server, comparing the consistency of the file in the standard area and the file in the working area, if the file is not consistent, downloading the file from the server to the interactive area, modifying and combining the downloaded file and the file in the working area, saving the combined file to the working area, and updating the version of the file in the working area.
2. The method for controlling version management of a multi-party interoperation file according to claim 1, further comprising the steps of:
if the file in the standard area is consistent with the file in the working area, downloading the file from the server to the working area, and updating the file version in the working area; or,
and if the file in the standard area is consistent with the file in the working area, downloading the file from the server to the interactive area, copying the downloaded file to the working area, and updating the file version in the working area.
3. The method for controlling version management of a multi-party interoperation file according to claim 2, further comprising the steps of:
when a file is updated from the server, if the file already exists in the working area and the version of the file in the working area is not lower than the version of the file in the server, the update is terminated.
4. The method for controlling version management of a multi-party interoperation file according to claim 3, further comprising the steps of:
when updating a file from a server, if the file does not exist in a working area, downloading the file from the server to the working area, and updating the file version in the working area; or downloading the file from the server to the interactive area, copying the downloaded file to the working area, and updating the file version in the working area.
5. The method for controlling version management of multi-party interoperation file as claimed in claim 4, wherein in the step of comparing the consistency of the file in the standard area with the file in the working area, whether the files are consistent is determined according to the calculation result of MD5 by calculating a message digest MD5 of the file in the local working area and an MD5 of the file in the standard area, respectively.
6. The method for controlling version management of multi-party interoperation file according to any one of claims 1 to 5, wherein after the file in the workspace is updated, the method further comprises the following steps:
and saving the updated file and the file version in the working area to the standard area.
7. The method for controlling version management of a multi-party interoperation file according to claim 6, further comprising the steps of:
when the user submits the file in the working area to the server, if the file exists in the server and the version number of the file in the server is higher than that of the file in the working area, the submitting operation is stopped, and the file is updated.
8. The method as claimed in claim 7, wherein the step of suspending the commit operation and updating the file includes directly downloading the file from the server to the interactive area, modifying and merging the downloaded file with the file in the working area, storing the merged file in the working area, and updating the version of the file in the working area.
9. The method as claimed in claim 8, wherein the file is submitted again after the file is updated.
10. The method for controlling version management of a multi-party interoperation file according to claim 9, further comprising the steps of:
when a user submits a file in a working area to a server, if the file does not exist in the server, the file in the working area is directly uploaded to the server, the version number of the uploaded file is updated, and the uploaded file and the version number thereof are stored in a local standard area.
11. The method for controlling version management of a multi-party interoperation file according to claim 10, further comprising the steps of:
when a user submits a file in a working area to a server, if the file exists in the server, the version number of the file in the server is compared with the version number of the file in the working area, if the version number of the file in the server is not higher than the version number of the file in the working area, the file in the working area is directly uploaded to the server, the version number of the uploaded file is updated, and the uploaded file and the version number thereof are stored in a local standard area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010106192986A CN102541941A (en) | 2010-12-31 | 2010-12-31 | Version management control method for multiple parties to co-operate file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010106192986A CN102541941A (en) | 2010-12-31 | 2010-12-31 | Version management control method for multiple parties to co-operate file |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102541941A true CN102541941A (en) | 2012-07-04 |
Family
ID=46348856
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010106192986A Pending CN102541941A (en) | 2010-12-31 | 2010-12-31 | Version management control method for multiple parties to co-operate file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102541941A (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103678525A (en) * | 2013-11-29 | 2014-03-26 | 创新科软件技术（深圳）有限公司 | Method for sharing one file by multiple users |
| CN103927152A (en) * | 2013-01-14 | 2014-07-16 | 北大方正集团有限公司 | File processing method and device |
| CN102811260B (en) * | 2012-08-10 | 2015-04-15 | 清华大学 | File cloud synchronizing system and method |
| WO2016000655A1 (en) * | 2014-07-03 | 2016-01-07 | U3D Limited | Home system establishing method |
| CN105871955A (en) * | 2015-01-21 | 2016-08-17 | 深圳市腾讯计算机系统有限公司 | Distributed file system-based processing method, server and client |
| CN106844210A (en) * | 2017-01-20 | 2017-06-13 | 网易（杭州）网络有限公司 | The acquisition methods and device of event modification information |
| CN106991176A (en) * | 2017-04-06 | 2017-07-28 | 广州视源电子科技股份有限公司 | File management method, device, equipment and storage medium |
| CN107203724A (en) * | 2017-05-18 | 2017-09-26 | 北京京东尚科信息技术有限公司 | File submits method and apparatus |
| CN107766314A (en) * | 2017-10-20 | 2018-03-06 | 网易（杭州）网络有限公司 | The data processing method and device of electrical form |
| CN107943620A (en) * | 2017-12-15 | 2018-04-20 | 安徽长泰信息安全服务有限公司 | A kind of data backup method and system standby based on cloud calamity |
| CN108431797A (en) * | 2015-12-28 | 2018-08-21 | 微软技术许可有限责任公司 | The Version Control of the memory savings of electronic document |
| CN109558421A (en) * | 2018-10-29 | 2019-04-02 | 中国建设银行股份有限公司 | Data processing method, system, device and storage medium based on caching |
| CN110110301A (en) * | 2019-05-09 | 2019-08-09 | 成都终身成长科技有限公司 | File editing method, device, system, client, server and storage medium |
| CN110196840A (en) * | 2019-05-22 | 2019-09-03 | 中至数据集团股份有限公司 | Document management method, device, readable storage medium storing program for executing and computer equipment |
| CN110765150A (en) * | 2019-11-01 | 2020-02-07 | 上海热像科技股份有限公司 | Management method, device, server, medium and system |
| CN111367563A (en) * | 2020-03-06 | 2020-07-03 | 中国银行股份有限公司 | Host version merging method and device |
| CN111542790A (en) * | 2018-05-17 | 2020-08-14 | 贝克霍夫自动化有限公司 | Method for processing software items |
| CN112286541A (en) * | 2020-11-03 | 2021-01-29 | 浪潮云信息技术股份公司 | File distribution method |
| WO2021073636A1 (en) * | 2019-10-18 | 2021-04-22 | 华为技术有限公司 | Code conflict resolution system and method, devices, apparatus, and medium |
| CN113577775A (en) * | 2021-08-02 | 2021-11-02 | 网易（杭州）网络有限公司 | Method and device for checking art resource file, electronic device and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999947A (en) * | 1997-05-27 | 1999-12-07 | Arkona, Llc | Distributing database differences corresponding to database change events made to a database table located on a server computer |
| US6490596B1 (en) * | 1999-11-09 | 2002-12-03 | International Business Machines Corporation | Method of transmitting streamlined data updates by selectively omitting unchanged data parts |
| CN101546318A (en) * | 2008-03-27 | 2009-09-30 | 林兆祥 | Data storage method based on version |
| CN101556583A (en) * | 2008-04-10 | 2009-10-14 | 上海宝康电子控制工程有限公司 | Method for efficiently controlling embedded linux file system version |
| CN101655845A (en) * | 2008-08-21 | 2010-02-24 | 北京亿企通信息技术有限公司 | Method for processing documents in multi-person collaboration working environment |
-
2010
- 2010-12-31 CN CN2010106192986A patent/CN102541941A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999947A (en) * | 1997-05-27 | 1999-12-07 | Arkona, Llc | Distributing database differences corresponding to database change events made to a database table located on a server computer |
| US6490596B1 (en) * | 1999-11-09 | 2002-12-03 | International Business Machines Corporation | Method of transmitting streamlined data updates by selectively omitting unchanged data parts |
| CN101546318A (en) * | 2008-03-27 | 2009-09-30 | 林兆祥 | Data storage method based on version |
| CN101556583A (en) * | 2008-04-10 | 2009-10-14 | 上海宝康电子控制工程有限公司 | Method for efficiently controlling embedded linux file system version |
| CN101655845A (en) * | 2008-08-21 | 2010-02-24 | 北京亿企通信息技术有限公司 | Method for processing documents in multi-person collaboration working environment |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102811260B (en) * | 2012-08-10 | 2015-04-15 | 清华大学 | File cloud synchronizing system and method |
| CN103927152B (en) * | 2013-01-14 | 2017-07-14 | 北大方正集团有限公司 | A kind of document handling method and device |
| CN103927152A (en) * | 2013-01-14 | 2014-07-16 | 北大方正集团有限公司 | File processing method and device |
| CN103678525A (en) * | 2013-11-29 | 2014-03-26 | 创新科软件技术（深圳）有限公司 | Method for sharing one file by multiple users |
| CN103678525B (en) * | 2013-11-29 | 2017-09-22 | 创新科软件技术（深圳）有限公司 | A kind of method of multiple users share identical file |
| WO2016000655A1 (en) * | 2014-07-03 | 2016-01-07 | U3D Limited | Home system establishing method |
| CN105871955A (en) * | 2015-01-21 | 2016-08-17 | 深圳市腾讯计算机系统有限公司 | Distributed file system-based processing method, server and client |
| CN105871955B (en) * | 2015-01-21 | 2019-01-22 | 深圳市腾讯计算机系统有限公司 | A kind of processing method and server and client based on distributed file system |
| CN108431797A (en) * | 2015-12-28 | 2018-08-21 | 微软技术许可有限责任公司 | The Version Control of the memory savings of electronic document |
| CN106844210A (en) * | 2017-01-20 | 2017-06-13 | 网易（杭州）网络有限公司 | The acquisition methods and device of event modification information |
| CN106844210B (en) * | 2017-01-20 | 2019-08-23 | 网易（杭州）网络有限公司 | The acquisition methods and device of event modification information |
| CN106991176A (en) * | 2017-04-06 | 2017-07-28 | 广州视源电子科技股份有限公司 | File management method, device, equipment and storage medium |
| CN107203724A (en) * | 2017-05-18 | 2017-09-26 | 北京京东尚科信息技术有限公司 | File submits method and apparatus |
| CN107203724B (en) * | 2017-05-18 | 2020-06-30 | 北京京东尚科信息技术有限公司 | File submission method and device |
| CN107766314A (en) * | 2017-10-20 | 2018-03-06 | 网易（杭州）网络有限公司 | The data processing method and device of electrical form |
| CN107766314B (en) * | 2017-10-20 | 2021-07-09 | 网易（杭州）网络有限公司 | Data processing method and device for electronic forms |
| CN107943620A (en) * | 2017-12-15 | 2018-04-20 | 安徽长泰信息安全服务有限公司 | A kind of data backup method and system standby based on cloud calamity |
| CN111542790A (en) * | 2018-05-17 | 2020-08-14 | 贝克霍夫自动化有限公司 | Method for processing software items |
| CN111542790B (en) * | 2018-05-17 | 2023-09-01 | 贝克霍夫自动化有限公司 | Method for processing software items |
| CN109558421A (en) * | 2018-10-29 | 2019-04-02 | 中国建设银行股份有限公司 | Data processing method, system, device and storage medium based on caching |
| CN110110301A (en) * | 2019-05-09 | 2019-08-09 | 成都终身成长科技有限公司 | File editing method, device, system, client, server and storage medium |
| CN110110301B (en) * | 2019-05-09 | 2023-08-01 | 成都终身成长科技有限公司 | File editing method, device, system, client, server and storage medium |
| CN110196840A (en) * | 2019-05-22 | 2019-09-03 | 中至数据集团股份有限公司 | Document management method, device, readable storage medium storing program for executing and computer equipment |
| WO2021073636A1 (en) * | 2019-10-18 | 2021-04-22 | 华为技术有限公司 | Code conflict resolution system and method, devices, apparatus, and medium |
| US11960879B2 (en) | 2019-10-18 | 2024-04-16 | Huawei Cloud Computing Technologies Co., Ltd. | Code conflict resolution system and method, apparatus, device, and medium |
| CN110765150A (en) * | 2019-11-01 | 2020-02-07 | 上海热像科技股份有限公司 | Management method, device, server, medium and system |
| CN111367563A (en) * | 2020-03-06 | 2020-07-03 | 中国银行股份有限公司 | Host version merging method and device |
| CN111367563B (en) * | 2020-03-06 | 2024-02-23 | 中国银行股份有限公司 | Host version merging method and device |
| CN112286541A (en) * | 2020-11-03 | 2021-01-29 | 浪潮云信息技术股份公司 | File distribution method |
| CN113577775A (en) * | 2021-08-02 | 2021-11-02 | 网易（杭州）网络有限公司 | Method and device for checking art resource file, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102541941A (en) | Version management control method for multiple parties to co-operate file | |
| CN110727954B (en) | Data authorization desensitization automation method, device and storage medium | |
| US20190278767A1 (en) | Smart contract upgrade method and system based on alliance chain | |
| US10353889B2 (en) | Monitoring alignment of computer file states across a group of users | |
| CN106599321B (en) | Plug-in for generation and analysis of DWG file annotation and signature and use method thereof | |
| US8595171B2 (en) | System and method for rule set validation | |
| US20120297363A1 (en) | Inferred and shared source control integration across mulitiple program development tools | |
| CN109634679B (en) | Block chain configuration updating method, device, equipment and storage medium | |
| US20180189690A1 (en) | Product development management system and method | |
| US20080072217A1 (en) | Method, apparatus, and system for customizing and performing policy in version control | |
| WO2019005351A1 (en) | Code review rebase diffing | |
| CN109643357A (en) | For the protection feature for the data being stored at storage service | |
| CN105302533A (en) | Code synchronizing method and apparatus | |
| CN113688618A (en) | Custom form-based field permission editing method and system | |
| US10452635B2 (en) | Synchronizing files on different computing devices using file anchors | |
| CN102708416A (en) | Method, device and system for ordering business by users | |
| CN110597662A (en) | Backup data automatic verification method and device, user equipment and storage medium | |
| CN115203648A (en) | Electronic book editing and checking method, device and system based on Git protocol | |
| CN111881475B (en) | Method for selecting role authority based on authority association | |
| US20240169320A1 (en) | Computer System and Methods for Managing Data, Data Access, and Data Retention | |
| EP3142320B1 (en) | Remote modification of a document database by a mobile telephone device | |
| CN110784353A (en) | Network element equipment configuration data migration method and device | |
| CN106547756B (en) | Database creation method and device | |
| US11206268B2 (en) | Account lifecycle management | |
| CN101634944A (en) | Interface method for ERP referencing WMS warehousing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20120704 |