Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: receiving a first synchronization request from a content management system for a client device, the first synchronization request including a namespace and a first path corresponding to a content item associated with the first synchronization request; determining that the namespace matches an entry in a namespace mount table, the entry comprising a second path associated with the namespace; determining that the client device does not use namespaces to synchronize content items associated with the content management system; prepending the second path associated with the namespace to the first path in the first synchronization request, to yield a third path; and sending, to the client device, a second synchronization request including the third path.
This invention relates to content synchronization in a content management system, specifically addressing the challenge of handling namespace-based synchronization requests for client devices that do not support namespace functionality. The method involves receiving a synchronization request from a content management system for a client device, where the request includes a namespace and a path corresponding to a content item. The system checks if the namespace matches an entry in a namespace mount table, which contains a second path associated with the namespace. If the client device does not use namespaces for synchronization, the system prepends the second path from the mount table to the original path in the request, creating a modified path. This modified path is then sent to the client device in a new synchronization request, ensuring compatibility with devices that lack namespace support. The solution enables seamless synchronization by dynamically adjusting paths based on namespace mappings, allowing content management systems to serve both namespace-aware and non-namespace-aware clients efficiently.
2. The method of claim 1 , further comprising: omitting the namespace from the second synchronization request.
A system and method for synchronizing data between a client device and a server involves transmitting a first synchronization request from the client to the server, where the request includes a namespace identifier. The server processes this request and returns a response containing data associated with the specified namespace. The client then generates a second synchronization request, which is sent to the server without including the namespace identifier. This second request is used to retrieve additional data or updates from the server, allowing the client to maintain an up-to-date dataset without repeatedly specifying the namespace. The method ensures efficient data synchronization by reducing redundant information in subsequent requests, thereby optimizing network traffic and processing time. The approach is particularly useful in distributed systems where multiple clients interact with a central server, requiring periodic data updates while minimizing overhead. The omission of the namespace in the second request streamlines communication, as the server can infer the relevant namespace from prior interactions or context, improving overall system performance.
3. The method of claim 1 , further comprising: determining whether a second client device uses namespaces to synchronize content items associated with the content management system; and when the second client device uses namespaces to synchronize content items associated with the content management system, sending, to the second client device, a third synchronization request including a fourth path comprising the namespace and the first path.
This invention relates to content synchronization in a content management system, specifically addressing the challenge of efficiently synchronizing content items between client devices that use different synchronization protocols. The system detects whether a client device employs namespaces to organize and synchronize content items. If a namespace is used, the system generates a synchronization request that includes both the namespace and the original content path, ensuring proper routing and synchronization of content items within the namespace structure. This approach prevents synchronization conflicts and ensures consistent content management across devices with varying synchronization capabilities. The method dynamically adapts to the client device's synchronization protocol, improving interoperability and reliability in distributed content management environments. The solution enhances synchronization accuracy by explicitly incorporating namespace information in synchronization requests, reducing errors and improving data consistency.
4. The method of claim 1 , further comprising: receiving a third synchronization request comprising an instruction to move a collection, the instruction including a new collection path and an old collection path; determining that a portion of the second path matches the old collection path; replacing the portion of the second path that matches the old collection path with the new collection path, to yield an updated entry path; and sending the third synchronization request to the content management system.
This invention relates to a method for synchronizing data paths in a content management system, particularly when collections are moved or renamed. The problem addressed is ensuring that references to moved or renamed collections remain valid during synchronization, preventing broken links or errors in the system. The method involves receiving a synchronization request that includes an instruction to move a collection, specifying both a new collection path and an old collection path. The system then checks if a portion of an existing path (e.g., a stored or referenced path) matches the old collection path. If a match is found, that portion is replaced with the new collection path, updating the entry path accordingly. This ensures that all references to the moved or renamed collection remain accurate. The updated synchronization request is then sent to the content management system, maintaining consistency across the system. Additionally, the method may involve receiving a first synchronization request to create or update an entry in the content management system, where the request includes a first path. The system then determines whether the first path is valid and, if not, rejects the request. If valid, the entry is created or updated with the first path. A second synchronization request may also be received, containing a second path, and the system checks if the second path is valid before processing it. This ensures that all paths in the system are correctly maintained, even when collections are moved or renamed.
5. The method of claim 4 , further comprising: sending, to the client device, a fourth synchronization request comprising the instruction to move the collection, the instruction including the updated entry path.
A system and method for synchronizing data collections between a server and a client device addresses the challenge of efficiently managing and updating hierarchical data structures in distributed environments. The invention involves a server that maintains a collection of data entries organized in a hierarchical path structure, where each entry has a unique path identifier. The server receives a synchronization request from a client device, which includes a request to move a specific data collection from one location to another within the hierarchy. The server processes this request by updating the entry path of the collection in its data store and then sends a synchronization response to the client device, confirming the change. The response includes the updated entry path to ensure the client device can reflect the new location of the collection. Additionally, the server may send a subsequent synchronization request to the client device, instructing it to move the collection to the updated path, thereby ensuring consistency between the server and client data structures. This method enables real-time synchronization of hierarchical data while minimizing conflicts and ensuring data integrity across distributed systems. The invention is particularly useful in cloud-based storage, collaborative editing tools, and distributed databases where maintaining synchronized hierarchical data structures is critical.
6. The method of claim 4 , wherein the instruction to move the collection comprises an instruction to rename the collection from an old collection name to a new collection name, wherein the old collection name is associated with the old collection path and the new collection name is associated with the new collection path.
This invention relates to data management systems, specifically methods for renaming collections within a storage system to facilitate data organization and access. The problem addressed is the need to efficiently relocate or reorganize collections of data while maintaining accessibility and integrity. A collection is a structured grouping of data, such as files or objects, stored under a specific path or identifier. The invention provides a method to rename a collection, where the old collection name is linked to an old storage path and the new collection name is linked to a new storage path. This renaming operation effectively moves the collection from the old path to the new path without disrupting data access. The method ensures that references to the collection are updated to reflect the new name and path, preventing broken links or errors. This approach simplifies data management by allowing administrators to reorganize collections dynamically while preserving their structure and content. The invention is particularly useful in distributed storage systems, cloud environments, or any system where collections must be relocated or renamed for organizational or operational reasons. The method may be part of a broader system for managing collections, including creating, deleting, or modifying them. The renaming process may involve validating the new name, updating metadata, and ensuring consistency across the system. This solution enhances flexibility in data storage and retrieval, improving efficiency and usability.
7. The method of claim 6 , wherein the second path includes the old collection name, wherein replacing the portion of the second path that matches the old collection path with the new collection path comprises replacing the old collection name in the second path with the new collection name.
This invention relates to data management systems, specifically methods for updating collection names in a database while maintaining data integrity and accessibility. The problem addressed is the need to efficiently rename collections in a database without disrupting existing references or breaking data links, which can lead to errors or data loss. The method involves updating paths in a database to reflect a new collection name while preserving the structure of the data. A first path is identified, which includes the old collection name, and a second path is identified that also includes the old collection name. The portion of the second path that matches the old collection path is replaced with the new collection path. Specifically, the old collection name in the second path is replaced with the new collection name. This ensures that all references to the old collection are updated to the new collection, maintaining consistency across the database. The method may also involve validating the new collection path to ensure it is correct and accessible before performing the replacement. This step helps prevent errors and ensures that the data remains intact and accessible after the rename operation. The approach is particularly useful in distributed databases or systems where multiple components rely on consistent naming conventions for data collections.
8. The method of claim 1 , further comprising: receiving a third synchronization request comprising an instruction to move a collection, the instruction including a new collection path and an old collection path; determining that an entry path in a second entry in the namespace mount table matches a first portion of the old collection path; determining that the entry path does not match a second portion of the new collection path; in response to determining that the entry path matches the first portion of the old collection path and does not match the second portion of the new collection path: removing the first portion of the old collection path; and modifying the third synchronization request to indicate that the old collection path is associated with a second namespace in the second entry; and sending the third synchronization request to the content management system.
This invention relates to a method for managing namespace synchronization in a content management system, particularly for handling collection path modifications. The problem addressed involves efficiently updating namespace mount tables when a collection is moved, ensuring proper synchronization between the namespace and the content management system. The method involves receiving a synchronization request to move a collection, which includes a new collection path and an old collection path. The system checks a namespace mount table to determine if an entry path matches a portion of the old collection path. If the entry path matches only a portion of the old path and not the corresponding portion of the new path, the system removes the matching portion of the old path from the entry. The synchronization request is then modified to indicate that the remaining old path is associated with a different namespace in the mount table. Finally, the updated request is sent to the content management system to complete the synchronization. This approach ensures that namespace mappings remain accurate when collections are relocated, preventing synchronization errors and maintaining data integrity across the system. The method dynamically adjusts namespace references to reflect path changes, improving reliability in distributed content management environments.
9. A non-transitory computer-readable medium comprising: computer-executable instructions stored thereon which, when executed by one or more processors, cause the one or more processors to: receive a first synchronization request from a content management system for a client device, the first synchronization request including a namespace and a first path corresponding to a content item associated with the first synchronization request; determine that the namespace matches an entry in a namespace mount table, the entry comprising a second path associated with the namespace; determine whether the client device uses namespaces to synchronize content items associated with the content management system; and when the client device does not use namespaces to synchronize content items associated with the content management system: prepend the second path associated with the namespace to the first path in the first synchronization request, to yield a third path; and send, to the client device, a second synchronization request including the third path.
This invention relates to content synchronization systems, specifically addressing the challenge of managing content paths in a namespace-aware content management system when synchronizing with client devices that do not support namespace-based synchronization. The system receives a synchronization request from a content management system for a client device, where the request includes a namespace and a path corresponding to a content item. The system checks if the namespace matches an entry in a namespace mount table, which contains a second path associated with the namespace. If the client device does not support namespace-based synchronization, the system prepends the second path from the namespace mount table to the original path in the synchronization request, creating a modified path. This modified path is then sent to the client device in a new synchronization request, ensuring compatibility with devices that do not use namespaces for content synchronization. The solution enables seamless synchronization between namespace-aware systems and devices that lack namespace support, maintaining data integrity and accessibility.
10. The non-transitory computer-readable medium of claim 9 , storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to: omit the namespace from the second synchronization request.
A system and method for optimizing data synchronization in distributed computing environments addresses inefficiencies in namespace handling during synchronization requests. The invention improves performance by selectively omitting namespace information from synchronization requests under specific conditions, reducing unnecessary data transmission and processing overhead. The system generates a first synchronization request that includes namespace information to establish a baseline for data consistency. Subsequently, a second synchronization request is generated, where the namespace is intentionally excluded to streamline the synchronization process. This approach is particularly useful in scenarios where the namespace remains unchanged between requests, eliminating redundant data transfers. The system may also validate the omission of the namespace to ensure data integrity and consistency. By dynamically adjusting the inclusion of namespace information based on contextual factors, the invention enhances synchronization efficiency while maintaining accuracy. The method is implemented through computer-executable instructions stored on a non-transitory computer-readable medium, executed by one or more processors to perform the described operations. This solution is applicable in distributed databases, cloud computing, and other systems requiring frequent data synchronization.
11. The non-transitory computer-readable medium of claim 9 , wherein the first synchronization request includes a second namespace, the method further comprising removing the second namespace from the first synchronization request.
This invention relates to data synchronization systems, specifically addressing the challenge of managing namespace conflicts during synchronization operations. The system involves a non-transitory computer-readable medium storing instructions for synchronizing data between a client and a server. The method includes receiving a first synchronization request from the client, where the request may contain a second namespace. The system processes this request by removing the second namespace before proceeding with the synchronization. This ensures that only the intended data is synchronized, preventing conflicts or unintended data transfers. The method also involves generating a first synchronization response based on the processed request and transmitting this response to the client. The synchronization response may include a first namespace, which the client uses to identify the synchronized data. The system further handles additional synchronization requests, such as a second synchronization request, which may include a third namespace. The method processes this request by removing the third namespace and generating a second synchronization response based on the processed request. This response is then transmitted to the client. The overall system ensures efficient and conflict-free data synchronization by dynamically managing namespaces within synchronization requests.
12. The non-transitory computer-readable medium of claim 9 , storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to: receive a third synchronization request comprising an instruction to move a collection, the instruction including a new collection path and an old collection path; determine that a portion of the second path matches the old collection path; replace the portion of the second path that matches the old collection path with the new collection path, to yield an updated entry path; and send the third synchronization request to the content management system.
This invention relates to a system for managing and synchronizing collections of data within a content management system. The problem addressed is the need to efficiently update and synchronize collection paths when a collection is moved or renamed, ensuring that all references to the collection remain valid and consistent across the system. The system involves a non-transitory computer-readable medium storing executable instructions that, when run by one or more processors, perform a synchronization process. The process begins by receiving a synchronization request that includes an instruction to move a collection, specifying both a new collection path and an old collection path. The system then checks if a portion of a second path (likely a reference path stored in the system) matches the old collection path. If a match is found, the system replaces that portion of the second path with the new collection path, resulting in an updated entry path. Finally, the system sends the updated synchronization request to the content management system, ensuring that all references to the moved collection are correctly updated. This approach automates the process of updating collection references, reducing manual intervention and minimizing errors in path management. The system ensures that all dependent paths are consistently updated when a collection is moved, maintaining data integrity and synchronization across the content management system.
13. The non-transitory computer-readable medium of claim 12 , storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to: send, to the client device, a fourth synchronization request comprising the instruction to move the collection, the instruction including the updated entry path.
A system and method for synchronizing data collections across multiple devices involves managing hierarchical data structures, such as file systems or database entries, to ensure consistency. The technology addresses the challenge of maintaining accurate and up-to-date data paths when collections are moved or renamed, which can disrupt synchronization processes. The system detects changes to entry paths within a collection and generates updated synchronization requests to propagate these changes to client devices. When a collection is moved, the system sends a synchronization request that includes an instruction to relocate the collection and an updated entry path, ensuring all devices reflect the correct hierarchical structure. This process involves tracking path modifications, validating the updated paths, and transmitting the changes to connected devices to maintain data integrity. The system may also handle conflicts or errors during synchronization, such as invalid paths or access restrictions, to ensure reliable data management. The solution is particularly useful in distributed environments where multiple devices need to access and modify shared data collections while maintaining consistency.
14. The non-transitory computer-readable medium of claim 12 , wherein the instruction to move the collection comprises an instruction to rename the collection from an old collection name to a new collection name, wherein the old collection name is associated with the old collection path and the new collection name is associated with the new collection path.
This invention relates to data management systems, specifically methods for renaming and relocating collections of data within a storage system. The problem addressed is the need to efficiently rename and move collections while maintaining data integrity and accessibility. The system involves a non-transitory computer-readable medium storing instructions for managing data collections. When a collection is moved, the system updates the collection's name and path to reflect its new location. The old collection name is associated with the original path, while the new collection name is linked to the new path. This ensures that references to the collection remain valid after the move. The system may also include instructions for validating the new path before the move and for handling conflicts or errors during the process. The invention improves data organization by allowing seamless renaming and relocation of collections without disrupting existing references or workflows. This is particularly useful in large-scale storage systems where collections may need to be reorganized frequently.
15. The non-transitory computer-readable medium of claim 14 , wherein the second path includes the old collection name, wherein replacing the portion of the second path that matches the old collection path with the new collection path comprises replacing the old collection name in the second path with the new collection name.
This invention relates to data management systems, specifically methods for updating references to collections in a database. The problem addressed is the need to efficiently update paths or references to collections when their names are changed, ensuring that all dependent data or references are correctly modified to reflect the new collection name. The system involves a non-transitory computer-readable medium storing instructions for performing operations. These operations include receiving a request to rename a collection from an old collection name to a new collection name. The system then identifies a second path that includes the old collection name. The system replaces the portion of the second path that matches the old collection path with the new collection path, specifically by replacing the old collection name in the second path with the new collection name. This ensures that all references to the old collection name are updated to the new collection name, maintaining data integrity and avoiding broken references. The invention also involves determining whether the second path includes the old collection name before performing the replacement. This step ensures that only relevant paths are modified, preventing unintended changes to unrelated data. The system may also validate the new collection name to ensure it meets naming conventions or other requirements before performing the update. This validation step helps maintain consistency and avoid errors in the database. The overall solution provides a robust method for updating collection references in a database, ensuring seamless transitions when collection names are changed.
16. A system comprising: one or more processors; and at least one computer-readable medium; and computer-readable instructions stored on the at least one computer-readable medium, that when executed by the one or more processors cause the system to: receive a first synchronization request from a content management system for a client device, the first synchronization request including a namespace and a first path corresponding to a content item associated with the first synchronization request; determine that the namespace matches an entry in a namespace mount table, the entry comprising a second path associated with the namespace; determine whether the client device uses namespaces to synchronize content items associated with the content management system; and when the client device does not use namespaces to synchronize content items associated with the content management system: prepend the second path associated with the namespace to the first path in the first synchronization request, to yield a third path; and send, to the client device, a second synchronization request including the third path.
This system addresses the challenge of synchronizing content items between a content management system and client devices that may or may not support namespace-based synchronization. The system includes processors and computer-readable storage containing instructions to handle synchronization requests. When a content management system sends a synchronization request for a client device, the request includes a namespace and a path to a content item. The system checks if the namespace matches an entry in a namespace mount table, which contains a corresponding path for that namespace. If the client device does not support namespace-based synchronization, the system modifies the original path by prepending the path from the namespace mount table to the original path, creating a new path. This modified path is then sent to the client device in a new synchronization request. This approach ensures compatibility between the content management system and client devices that lack namespace support, enabling seamless content synchronization regardless of the client's capabilities. The system dynamically adjusts synchronization requests to maintain consistency across different client configurations.
17. The system of claim 16 , wherein the computer-readable instructions, when executed by the one or more processors, cause the one or more processors to: omit the namespace from the second synchronization request.
This invention relates to a system for synchronizing data between a client device and a server, addressing the challenge of efficiently managing data updates while minimizing network overhead. The system includes a client device with one or more processors and a server with one or more processors, both configured to exchange synchronization requests and responses. The client device generates a first synchronization request containing a namespace identifier to specify a subset of data for synchronization. The server processes this request, identifies changes in the specified namespace, and generates a second synchronization request to propagate those changes back to the client. The second synchronization request includes the same namespace identifier as the first request, ensuring consistency in data updates. The system further optimizes communication by omitting the namespace from the second synchronization request when the server determines that the namespace is already known or redundant, reducing unnecessary data transmission. This approach improves synchronization efficiency by minimizing redundant information while maintaining accurate data updates between the client and server.
18. The system of claim 16 , wherein the computer-readable instructions, when executed by the one or more processors, cause the one or more processors to: determine whether a second client device uses namespaces to synchronize content items associated with the content management system; and when the second client device uses namespaces to synchronize content items associated with the content management system, sending, to the second client device, a third synchronization request including a fourth path comprising the namespace and the first path.
A content management system synchronizes files and folders across multiple client devices. A challenge arises when different client devices use different synchronization methods, particularly when some devices rely on namespace-based synchronization. Namespace-based synchronization involves organizing content items (e.g., files or folders) into distinct logical groups, often using unique identifiers or paths that include namespace information. This can complicate synchronization when a device does not support namespaces, leading to potential conflicts or incomplete synchronization. The system addresses this by detecting whether a client device uses namespace-based synchronization. If the device does, the system sends a synchronization request that includes both the namespace and the original file path. This ensures that the device can correctly interpret and synchronize the content items, maintaining consistency across all connected devices. The system dynamically adjusts synchronization requests based on the capabilities of each client device, improving reliability and compatibility in distributed content management environments. This approach prevents synchronization errors and ensures seamless file access regardless of the device's synchronization method.
19. The system of claim 16 , wherein the computer-readable instructions, when executed by the one or more processors, cause the one or more processors to: receive a third synchronization request comprising an instruction to move a collection, the instruction including a new collection path and an old collection path; determine that a portion of the second path matches the old collection path; replace the portion of the second path that matches the old collection path with the new collection path, to yield an updated entry path; and send the third synchronization request to the content management system.
This invention relates to a system for managing and synchronizing collections of data within a content management system. The problem addressed is the need to efficiently update and synchronize collection paths when collections are moved or renamed, ensuring that all references to the collection remain valid and consistent across the system. The system includes a synchronization module that processes synchronization requests to update collection paths. When a request is received to move a collection, the system identifies the old and new collection paths. If a portion of an existing path matches the old collection path, that portion is replaced with the new collection path, generating an updated entry path. This ensures that all references to the moved collection are automatically updated to reflect the new location. The updated synchronization request is then sent to the content management system to propagate the changes. The system also includes a storage module that stores collection data and a communication module that facilitates interactions with the content management system. The synchronization module processes multiple types of synchronization requests, including those for moving, renaming, or updating collections, ensuring seamless synchronization across the system. The invention improves data management by maintaining accurate and up-to-date references to collections, reducing errors and inconsistencies in the content management system.
20. The system of claim 19 , send, to the client device, a fourth synchronization request comprising the instruction to move the collection, the instruction including the updated entry path.
This invention relates to a distributed data synchronization system for managing and updating collections of data entries across multiple client devices. The system addresses the challenge of maintaining consistency and accessibility of data collections when changes occur, such as when a collection is moved or renamed. The system includes a server that tracks the state of data collections and their entry paths, ensuring that client devices receive accurate and up-to-date information. When a collection is moved, the server generates an updated entry path reflecting the new location. The system then sends a synchronization request to the client device, instructing it to update its local copy of the collection using the new path. This ensures that all client devices maintain synchronized access to the collection, even after structural changes. The system may also handle conflicts or errors during synchronization, such as when a client device is offline or when multiple changes occur simultaneously. The invention improves data consistency and user experience in distributed environments by automating the propagation of collection updates across devices.
Unknown
April 14, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.