Manifest-Driven Loader for Web Bundle Versioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web applications hosted on cloud servers face risks of hardware/software damage due to executed scripts or plug-ins, and challenges arise when updating third-party plug-ins without access to their code, leading to potential inoperability of multiple plug-ins.
Innovation Solution
Shift the execution of web applications from server-side to client-side using TypeScript or JavaScript, generating web packages and manifest files to manage script modules, and implementing a bundle manifest system for versioning and compatibility checking of bundle components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web applications are executed on cloud servers, then user experience and functionality are enhanced, but hardware and software components of the servers may be damaged intentionally or accidentally
Solution Approach 1:
The patent extracts the web application execution environment from the cloud server and relocates it to the client device. By generating a page model that includes a module loader and script modules, the execution is shifted to the client side, preventing potential damage to server hardware and software while maintaining application functionality.
Solution Approach 2:
The patent introduces a page model as an intermediary between the cloud server and the client device. The page model contains a module loader and script modules that enable client-side execution, acting as a mediator that transfers application functionality from the server to the client without direct server execution of user-generated scripts.
2Reliability
If third-party plug-ins are updated without access to their code, then security and functionality may be improved, but multiple plug-ins may become inoperable due to compatibility issues
Solution Approach 1:
The patent implements preliminary version identification and dependency mapping for all script modules during the page model generation phase. By pre-identifying version requirements and dependencies, the system can ensure compatibility when updating third-party plug-ins, preventing inoperability issues while maintaining security and functionality.
Solution Approach 2:
The patent establishes a feedback mechanism through the manifest file that tracks version information and dependencies of all script modules. This feedback system allows the module loader to verify compatibility before loading updated plug-ins, ensuring that security and functionality improvements do not break existing plug-in operations.
3Object-affected harmful factors
If client-side execution is implemented, then server security is improved, but management and coordination of multiple script modules become more complex
Solution Approach 1:
The patent merges the management of multiple script modules into a unified page model structure with a single module loader. This consolidation simplifies client-side execution management by providing a centralized mechanism to load, coordinate, and manage all script modules, reducing the complexity that would otherwise arise from managing multiple independent scripts.
Solution Approach 2:
The patent transforms the complexity of script module management into manageable parameters through the manifest file, which explicitly defines version requirements, dependencies, and loading sequences. By parameterizing module information, the system makes complex coordination tasks tractable and systematic.
Data Source
AI summary
Computer systems, devices, and associated methods of loading a bundle component, comprising a bundle of scripts and a manifest including metadata for the bundle, that is compatible with a dependent bundle component are disclosed herein. In one embodiment, a method includes identifying a bundle component identifier and a version identifier for the bundle component that the dependent bundle component depends on in a manifest associated with the dependent bundle component. The method then includes retrieving a manifest for a bundle component that includes the bundle component identifier and is a most recent compatible version of the bundle component. The method includes loading the most recent compatible bundle component based on a URL in the retrieved manifest for the bundle component.