In-App File Topology Changes During Remote Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing productivity applications do not allow users to rename or move files while they are open for editing, leading to inefficiencies and synchronization issues, especially when files are stored remotely, requiring users to exit the application and use separate tools, causing delays and potential loss of edits.
Innovation Solution
A method and system that enables users to rename and move files within a productivity application while the file is open, allowing synchronization with remote storage services, by communicating requests directly to the synchronization application and updating metadata to reflect changes, enabling simultaneous editing and synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users rename or move files using separate applications like File Explorer, then file location changes can be made, but users must exit the productivity application and coordinate steps across multiple applications, leading to time loss and reduced productivity
Solution Approach 1:
The patent combines file management capabilities (rename, move) directly into the productivity application interface. Users can now perform topological changes to files through the productivity application itself rather than switching to File Explorer, merging two previously separate functions into one unified application.
Solution Approach 2:
The productivity application is enhanced to serve multiple functions: it not only performs document editing but also handles file management operations such as renaming and moving files. This multi-functionality eliminates the need to use separate applications for file management.
2Reliability
If users wait for synchronization to complete before renaming or moving files, then synchronization issues are avoided, but task completion is delayed and efficiency is reduced
Solution Approach 1:
The system performs preliminary validation of the requested directory location before executing the rename or move operation. The productivity application communicates with the synchronization application to check if the location is valid, preventing synchronization conflicts before they occur.
Solution Approach 2:
The system implements a feedback mechanism where the productivity application communicates with the synchronization application to verify the validity of the requested directory location. This feedback loop ensures that operations are only performed when they will not cause synchronization issues, maintaining reliability while enabling continuous workflow.
3Reliability
If files are locked during editing to prevent synchronization conflicts, then data integrity is maintained, but users cannot perform topological changes while the file is open
Solution Approach 1:
The patent implements dynamic file locking mechanisms that adapt based on the type of operation being performed. The system can grant or deny locking requests depending on whether the operation is an edit or a topological change, and depending on the synchronization state of the file. This dynamic approach allows flexibility in file operations while maintaining data integrity.
Solution Approach 2:
The synchronization application autonomously manages file locking and unlocking based on synchronization state. When a file is synchronized, the system automatically updates the locking status, allowing productivity applications to perform operations without manual intervention while maintaining data integrity through automated conflict prevention.
4Ease of manufacture
If users interact with operating system file explorers to rename/move files, then file system changes can be made, but the process is cumbersome and requires coordination between multiple applications
Solution Approach 1:
The patent merges file management functionality into the productivity application, eliminating the need to switch between the productivity application and File Explorer. Users can perform all file operations directly within the productivity application interface, simplifying the workflow.
Solution Approach 2:
The system introduces an intermediary communication protocol between the productivity application and the synchronization application. This intermediary layer handles the complexity of coordination automatically, allowing users to interact with a simple interface while the system manages the complex synchronization and file system operations in the background.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system is provided for enabling in-application support for topological changes to local files during remote synchronization. The techniques disclosed herein solve the problems of existing systems by mitigating conflict states and loss of edits being made to a file during synchronization. In addition, the techniques disclosed herein enable a user to interact directly with a productivity application to rename and/or move a file. The techniques disclosed herein provide an improved user experience and more efficient methods for interacting with files in that a user does not have to exit a productivity application and interact with an operating system interface to rename and/or move a file. A productivity application can operate in a server mode or a client mode depending on a validity of a requested destination location for a file.