Application Loading via Method Tag Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for improving application loading performance are limited to the file/module level, resulting in prolonged loading times for large web applications, causing inconvenience to users due to the transmission and loading of unnecessary codes.
Innovation Solution
A method and system that employs tagging of user action handler methods, replacing their content bodies with method tags, allowing only necessary codes to be loaded initially, and retrieving the actual content bodies from a method tag index store upon user interaction, thereby reducing redundant code loading and accelerating application loading.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all user action handler methods are loaded initially, then complete functionality is available, but loading time increases significantly
Solution Approach 1:
The patent segments user action handler methods into two categories: those required for UI generation (loaded initially) and those triggered by user interactions (loaded on-demand). This segmentation allows the system to load only essential methods initially, reducing loading time while maintaining UI generation functionality. When users trigger specific actions, the corresponding handler methods are then loaded from the server.
Solution Approach 2:
The patent performs preliminary action by pre-loading only the user action handler methods necessary for UI generation, rather than loading all methods. This preliminary selective loading reduces initial loading time while ensuring that essential functionality is available. Additional methods are loaded later as needed based on actual user interactions.
2Loss of time
If tagging method is implemented to reduce initial loading, then loading time decreases, but system complexity increases
Solution Approach 1:
The patent introduces a tagging mechanism as an intermediary between the client and the full method library. Tags serve as lightweight placeholders that reference actual user action handler methods on the server. This intermediary approach allows the client to work with minimal initial code while maintaining the ability to access complete functionality when needed, balancing loading performance with system capability.
3Productivity
If only essential methods are loaded initially, then loading performance improves, but functionality may be incomplete
Solution Approach 1:
The patent implements a dynamic loading strategy where the set of loaded methods evolves based on actual usage. Initially, only essential methods for UI generation are loaded. As users interact with the application and trigger specific actions, additional handler methods are dynamically loaded from the server. This dynamic approach ensures that functionality completeness matches actual user needs rather than providing all possible functions upfront.
Data Source
AI summary
The present invention discloses a method and system for application loading, the method comprising: receiving from the client a method tag request triggered on the basis of the tagging method of the application; retrieving the method tag in a method tag index store; obtaining, in response to the method tag being retrieved, a method content body corresponding to the method tag; and sending the method content body to the client. The present invention reduces the number of redundant codes to be loaded, thereby accelerating the application loading time.