Client File Cache with On-Demand Server Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current file management systems face challenges in providing ubiquitous access to files across multiple devices, efficient synchronization, and data backup, leading to issues such as version management conflicts and data loss due to inadequate backup practices.
Innovation Solution
A file management system that stores metadata and content in a client database with a subset of content cached locally, allowing on-demand retrieval of full content from a remote server, enabling seamless synchronization and access across devices while minimizing storage requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If all file content is stored locally on the client device, then access speed and availability are improved, but storage requirements and device complexity increase
Solution Approach 1:
The patent segments file data into metadata and content, storing metadata locally in the client database while keeping content on the server. This allows fast access to file information and selection while minimizing local storage requirements, as only essential metadata needs to be cached on the client device.
Solution Approach 2:
The patent introduces a network dimension by implementing a client-server architecture where files can be accessed remotely over a network. This allows files to be available across multiple devices without duplicating storage on each device, solving the storage constraint while maintaining accessibility.
2Ease of operation
If file content is cached locally on the client device, then access availability is improved, but storage requirements increase
Solution Approach 1:
The patent applies local quality by caching only essential metadata locally on the client device while keeping the actual file content on the server. This selective local storage provides sufficient information for file management operations without requiring full content duplication, thus maintaining ease of operation with minimal storage consumption.
3Productivity
If metadata is stored separately from content, then data management efficiency is improved, but system complexity increases
Solution Approach 1:
The patent introduces a metadata database as an intermediary layer between the client interface and the file content storage. This metadata layer manages file information, permissions, and access control without requiring direct manipulation of content files, thereby improving data management efficiency while keeping the system architecture manageable through clear separation of concerns.
Data Source
AI summary
Metadata for a set of files in a file system is stored in a client metadata database. In addition, a subset of content for the set of files in the client metadata database is stored in a client content database. The subset of content does not exceed a cache size that is less than a full size of the content in the set of the files. In response to a request, at least a portion of the content that is not already stored in the client content database is retrieved from a server content database, where the server content database is located remotely from the client device.