Running Application Self-Update via File Renaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating running applications on computing devices often require termination, leading to premature completion of tasks and network overload, and lack efficient self-update capabilities, especially in networked environments.
Innovation Solution
The system renames in-use application files, allowing for seamless self-update by storing new files in the same folder, executing the new application if setup is successful, and deferring actions to the newly updated version, while maintaining the old application's functionality until the update is complete.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the application is terminated to update the file, then the new application file can be installed, but the application tasks complete prematurely and network operations are disrupted
Solution Approach 1:
The system renames the old application file to a backup version (e.g., adding '.old' extension) before installing the new application file. This preliminary action preserves the old version while allowing the new version to be installed without terminating the running application, thus avoiding premature task completion and network disruptions
Solution Approach 2:
The renaming operation serves as an intermediary mechanism between the old and new application versions. By creating a renamed backup of the old file, the system enables seamless transition to the new version while maintaining application continuity, preventing both update failures and premature terminations
2Productivity
If the application continues running during update, then tasks complete successfully, but the old application file cannot be replaced
Solution Approach 1:
The system performs the file renaming operation before the application needs to access the updated file. By renaming the old file to a backup version in advance, the system ensures that when the application continues running and completes its tasks, the new application file is already in place and can be successfully activated afterward
3Productivity
If multiple applications are updated simultaneously on a network, then update efficiency increases, but network overload occurs
Solution Approach 1:
The system renames application files locally on each computing device before downloading or installing updates. This preliminary local operation reduces the need for simultaneous network access and file operations across multiple devices, thereby decreasing network traffic and preventing network overload while maintaining efficient update deployment
Solution Approach 2:
Each computing device performs self-service by renaming its own application files locally without requiring centralized coordination or simultaneous network access. This autonomous approach allows multiple devices to update independently and concurrently without creating network bottlenecks, thus maintaining high update efficiency while avoiding network overload
Data Source
AI summary
A computing device configured for updating a running application is described. The computing device includes a processor and instructions stored in memory. The computing device executes an old application. The computing device also renames an old application file that is currently in use. Furthermore, the computing device stores a new application file in the same folder as the old application file. The computing device additionally determines whether a new application is set up successfully. The computing device further executes the new application if the new application is set up successfully.