Document management and collaboration system
US-2015134600-A1 · May 14, 2015 · US
US10922333B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10922333-B2 |
| Application number | US-201715858110-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 29, 2017 |
| Priority date | Dec 28, 2017 |
| Publication date | Feb 16, 2021 |
| Grant date | Feb 16, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The disclosed technology relates to a system configured to identify a first operation in a first set of operations configured to converge a server state and a file system state, wherein the first operation is not in a second set of operations generated in response to an change to at least one of the server state and the file system state. The system is further configured to cancel the first operation, identify a second operation in both the first set of operations and the second set of operations, and initiate execution of the second operation concurrently with the canceling of the first operation.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: receiving a first set of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device; receiving a second set of operations, prior to completing executing the first set of operations, the second set of operations configured to converge the server state and the file system state after a client synchronization service identifies a change to at least one of the server state and the file system state; identifying a first operation in the first set of operations that is not in the second set of operations; initiating canceling the first operation; identifying a second operation in both the first set of operations and the second set of operations; and initiating execution of the second operation without waiting for the cancellation of the first operation to be completed. 2. The computer-implemented method of claim 1 , further comprising: identifying a third operation in the second set of operations that is not in the first set of operations; determining that the canceling of the first operation has completed; and initiating, in response to the determining, execution of the third operation. 3. The computer-implemented method of claim 1 , further comprising initiating execution of the first set of operations. 4. The computer-implemented method of claim 1 , wherein each operation in the first set of operations is configured to be concurrently executable and each operation in the second set of operations is configured to be concurrently executable. 5. The computer-implemented method of claim 1 , wherein initiating execution of the second operation comprises: identifying a script associated with the second operation, wherein the script defines multiple steps to be performed to complete the second operation; and executing the script. 6. The computer-implemented method of claim 1 , wherein initiating execution of the second operation comprises: transmitting instructions associated with the second operation to the content management system for execution on the server state. 7. The computer-implemented method of claim 1 , wherein initiating execution of the second operation comprises: transmitting instructions associated with the second operation to the client device for execution on the file system state. 8. The computer-implemented method of claim 1 , further comprising: identifying a first difference between a sync tree and at least one of a remote tree and a local tree, wherein the sync tree represents a known synced state between the server state and the file system state, the remote tree represents the server state, and the local tree represents the file system state; and generating, based on the first difference, the first set of operations configured to converge the server state and the file system state. 9. The computer-implemented method of claim 8 , further comprising: identifying a second difference between the sync tree and at least one of the remote tree and the local tree; and generating, based on the second difference, the second set of operations configured to converge the server state and the file system state after a change to at least one of the server state and the file system state. 10. The computer-implemented method of claim 8 , further comprising: receiving server modification data for content items stored by a content management service; and updating, based on the server modification data, the remote tree. 11. The computer-implemented method of claim 8 , further comprising: receiving client modification data for content items stored by the client device; and updating, based on the client modification data, the local tree. 12. A non-transitory computer-readable medium comprising instructions, the instructions, when executed by a computing system, cause the computing system to: receive a first set of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device; receive a second set of operations, prior to completing executing the first set of operations, the second set of operations configured to converge the server state and the file system state after a client synchronization service identifies a change to at least one of the server state and the file system state; identify a first operation in the first set of operations that is not in the second set of operations; initiate canceling the first operation; identify a second operation in the second set of operations that is not in the first set of operations; and initiate execution of the second operation without waiting for the cancellation of the first operation to be completed. 13. The non-transitory computer-readable medium of claim 12 , wherein the instructions further cause the computing system to: identify a third operation in both the first set of operations and the second set of operations; and initiate execution of the third operation concurrently with the initiating canceling of the first operation. 14. The non-transitory computer-readable medium of claim 12 , wherein each of the operations in the first set of operations is configured to be concurrently executable and each of the operations in the second set of operations is configured to be concurrently executable. 15. The non-transitory computer-readable medium of claim 12 , wherein the instructions to initiate execution of the second operation cause the computing system to: transmit instructions associated with the second operation to the at least one of the content management system for execution on the server state or the client device for execution on the file system state. 16. The non-transitory computer-readable medium of claim 12 , wherein the instructions further cause the computing system to: identify a difference between a sync tree and at least one of a remote tree and a local tree, wherein the sync tree represents a known synced state between the server state and the file system state, the remote tree represents the server state, and the local tree represents the file system state; and generate, based on the difference, the second set of operations configured to converge the server state and the file system state. 17. A system comprising: one or more processors; and a non-transitory computer-readable medium storing instructions that, when executed by the processor, cause the one or more processors to: identify a first operation in a first set of operations configured to converge a server state representing content items stored on a server of a content management system and a file system state representing content items stored on a client device, wherein the first operation is not in a second set of operations generated in response to a change to at least one of the server state and the file system state; initiate cancelling the first operation; identify a second operation in both the first set of operations and the second set of operations; and initiate execution of the second operation without waiting for the cancellation of the first operation to be completed. 18. The system of claim 17 , wherein the instructions further cause the one or more processors to: identify a third operation in the second set of operations that is not in the first set of operations; determine that canceling of the first operation has complet
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14) · CPC title
Protocols · CPC title
Change logging, detection, and notification (replication G06F16/27) · CPC title
Details of migration of file systems (migration mechanisms in storage systems G06F3/0647) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.