File Sync Hash Metadata Rename Move Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current file synchronization systems face challenges in efficiently detecting and managing file renames and moves across multiple computing devices, leading to unnecessary data retransmissions and deletion/recreation processes.
Innovation Solution
The system employs hash identifiers to encode files and folders within metadata, allowing for the identification of renamed or moved files and folders, and reorders synchronization operations to avoid deleting and recreating files, instead performing moves and renames directly, thus optimizing data transfer and reducing redundant processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional file synchronization methods are used, then file updates are replicated across computing devices, but renamed or moved files are incorrectly deleted and recreated, causing unnecessary data retransmissions and synchronization inefficiency
Solution Approach 1:
The system performs preliminary actions by creating metadata before synchronization occurs. This metadata includes hash identifiers and filenames that are used to identify renamed or moved files during the synchronization process, allowing the system to recognize these files and avoid unnecessary deletion and recreation operations.
Solution Approach 2:
The system uses feedback mechanisms by comparing current metadata with previous metadata to detect file renames and moves. This comparison feedback allows the synchronization system to identify when files have been renamed or moved and adjust its behavior accordingly, preventing incorrect deletion and recreation operations.
2Reliability
If files are synchronized by deleting and recreating, then consistency is maintained across devices, but redundant processes are executed and data transfer is wasted
Solution Approach 1:
The system employs feedback by comparing metadata between different states to detect file renames and moves. This metadata comparison feedback enables the system to distinguish between actual file changes and renames/moves, allowing it to maintain consistency without executing redundant deletion and recreation processes.
Solution Approach 2:
The system uses metadata copying instead of full file copying during synchronization. By copying and comparing metadata (hash identifiers and filenames) rather than copying actual file data, the system can efficiently identify renamed or moved files and avoid unnecessary data retransmissions while maintaining consistency.
3Difficulty of detecting and measuring
If hash identifiers are used to identify files, then renamed or moved files can be detected, but metadata management complexity increases
Solution Approach 1:
The system extracts only the essential metadata elements (hash identifiers and filenames) needed for file identification and comparison. By taking out only these critical components rather than managing complete file metadata, the system simplifies metadata management while maintaining the ability to detect file renames and moves effectively.
Data Source
AI summary
A method for synchronizing files is provided. Current metadata including a filename and a hash identifier for each file of the synchronized folder is created. The current metadata is compared to previous metadata. Based on the comparison, a first file and a first folder added to the synchronized folder and a second file and a second folder deleted from the synchronized folder are identified. The hash identifiers of the first and second files are compared. If the hash identifiers match, the filenames of the first and second files are compared. If the filenames do not match, the first file is identified as a renamed file. Metadata is sent to a synchronized device with information related to the first folder sent before information related to the first file, which is sent before information related to the second folder.