Document management and collaboration system
US-2015134600-A1 · May 14, 2015 · US
US10866964B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10866964-B2 |
| Application number | US-201715858125-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 29, 2017 |
| Priority date | Dec 28, 2017 |
| Publication date | Dec 15, 2020 |
| Grant date | Dec 15, 2020 |
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 detect a first file event associated with a content item on a local file system of a client device, determine that the first file event violates a local tree constraint in a set of local tree constraints, perform a remediation associated with the violated local tree constraint, and update a local tree based on the set of observed file events, wherein the local tree represents the file system state.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method performed by a client synchronization service, the computer-implemented method comprising: identifying a difference between a local tree that represents a previous state of a local file system and a current state of the local file system of a client device, wherein the local tree is stored on the client device; generating a first file event associated with a content item based on the identified difference between the local tree and the local file system of the client device; adding the first file event to a set of observed file events; determining that the set of observed file events violates a local tree constraint in a set of local tree constraints, wherein the local tree constraint comprises a requirement that all structures necessary to update the local tree are present in the set of observed file events or that data associated with the set of observed file events complies with at least one rule of the client synchronization service which must be fulfilled; performing a remediation associated with the violated local tree constraint; and updating the local tree based on the set of observed file events after performing the remediation associated with the violated local tree constraint. 2. The computer-implemented method of claim 1 , wherein the first file event is one of an add, a delete, an edit, or a move of the content item on the local file system of the client device. 3. The computer-implemented method of claim 1 , wherein the local tree constraint is a requirement that all nodes in the local tree must have an existing parent in order to have all structures necessary to update the local tree, and wherein the remediation associated with the violated local tree constraint is requiring observing a second file event associated with an add of a parent of the content item associated with the first file event. 4. The computer-implemented method of claim 3 , further comprising: detecting the second file event associated with the add of the parent of the content item; and adding the second file event to the set of observed file events. 5. The computer-implemented method of claim 1 , wherein the local tree constraint is a requirement that all nodes in the local tree have a unique file identifier in order to complied with the at least one rule of the client synchronization service, and wherein the remediation is assigning the content item associated with the first file event a new file identifier. 6. The computer-implemented method of claim 5 , further comprising: requesting, from a content management system, the new file identifier; and assigning the new file identifier for the content item associated with the first file event. 7. The computer-implemented method of claim 1 , wherein the remediation is editing a file name for the content item associated with the first file event. 8. The computer-implemented method of claim 1 , further comprising identifying a difference between the local tree and the local file system, wherein the first file event is based on the difference between the local tree and the local file system. 9. The computer-implemented method of claim 1 , further comprising determining, after the performing of the remediation, that the set of observed file events satisfies the set of local tree constraints, wherein the updating of the local tree is based on satisfaction of the set of local tree constraints. 10. The computer-implemented method of claim 1 , further comprising: determining that a server state and a last known state of the local file system are out of sync, wherein the determining is based on a difference between the local tree and a sync tree representing a known synced state between the server state and the last known state of the local file system; generating, based on the difference, a set of operations for the content items stored by a content management system, wherein the set of operations is configured to operate on the content items stored by the content management system to converge the server state and the last known state of the local file system; and managing execution of the set of operations. 11. A non-transitory computer readable medium comprising instructions, the instructions, when executed by a computing system including a client synchronization service, cause the client synchronization service to: identify a difference between a local tree that represents a previous state of a local file system and a current state of the local file system of a client device; generate a first file event associated with a content item based on the identified difference between the local tree and the local file system of the client device; determine that the first file event violates a local tree constraint in a set of local tree constraints, wherein the local tree constraint comprises a requirement that all structures necessary to update the local tree are present in a set of observed file events or that data associated with the set of observed file events complies with a rule of the client synchronization service which must be fulfilled; perform a remediation associated with the violated local tree constraint; and update the local tree based on the first file event after perform the remediation associated with the violated local tree constraint. 12. The non-transitory computer readable medium of claim 11 , wherein the first file event is one of an add, a delete, an edit, or a move of the content item on the local file system of the client device. 13. The non-transitory computer readable medium of claim 11 , wherein the instructions further cause the computing system to identify a difference between the local tree and the local file system, wherein the first file event is based on the difference between the local tree and the local file system. 14. The non-transitory computer readable medium of claim 11 , wherein the instructions further cause the computing system to: determine, based on a difference between the local tree and a sync tree representing a known synced state between a server state and the last known state of the local file system, that the server state and the last known state of the local file system are out of sync; generate, based on the difference, a set of operations for the content items stored by a content management system, wherein the set of operations is configured to operate on the content items stored by the content management system to converge the server state and the last known state of the local file system; and manage execution of the set of operations. 15. A system comprising: a one or more processors; and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to: identify a difference between a local tree that represents a previous state of a local file system and a current state of the local file system of a client device; generate a first file event associated with a content item based on the identified difference between the local tree and the local file system of the client device; add the first file event to a set of observed file events; determine that the first file event violates a local tree constraint in a set of local tree constraints, wherein the local tree constraint comprises a requirement that all structures necessary to update the local tree are present in the set of observed file events or that data associated with the set of observed file events complies with a rule of a synchronization service which must be fulfilled; perform a remediation associated with the violated lo
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
using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.