Dynamic Resource Management via Script Tag Bundling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web technologies generate excessive network traffic due to multiple HTTP requests for resource retrieval, especially when displaying messages in web applications, as there is no standard mechanism for running platform-independent languages like Java within browsers, leading to inefficient resource management.
Innovation Solution
Implementing a dynamic resource management method where a script tag on a web page points to a server-side script that compiles all resource codes into a single file, which is then cached on the client browser, reducing network traffic and improving response times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If resources are retrieved via multiple HTTP requests for each resource bundle, then resource availability is ensured, but network traffic becomes excessive
Solution Approach 1:
The patent combines multiple separate resource files into a single bundled resource file that contains all necessary resources (images, stylesheets, scripts) for a web page. This single file is transmitted to the client in one HTTP request, eliminating the need for multiple separate requests and significantly reducing network traffic while ensuring all resources are available.
Solution Approach 2:
The patent performs preliminary action by pre-bundling all resources into a single file before transmission. The resource bundling process aggregates multiple resources in advance, so when the client requests the web page, all resources are already packaged together and can be delivered in one operation, preventing the need for subsequent individual resource requests.
2Ease of operation
If resources are downloaded on first access and loaded to cache, then resource availability is improved, but initial network traffic increases significantly
Solution Approach 1:
The patent merges multiple resources into a single bundled file that is downloaded once. This approach ensures all resources are available in the cache after a single download, eliminating the need for subsequent downloads while minimizing the initial network traffic compared to downloading each resource separately.
Solution Approach 2:
The bundled resource file serves multiple functions simultaneously: it contains the HTML structure, embedded stylesheets, embedded scripts, and embedded images all in one file. This multi-functional approach ensures all resources are available without requiring separate download operations for each resource type.
3Adaptability or versatility
If platform-independent languages like Java are used with robust message mechanisms, then message display capability is improved, but a standard browser-running mechanism is unavailable
Solution Approach 1:
The patent extracts the platform-dependent Java message mechanisms from the server-side environment and embeds them directly into the HTML resource file as JavaScript code. This extraction allows the message display functionality to run natively in the browser without requiring Java runtime or other platform-specific environments, achieving browser compatibility while maintaining adaptability.
Solution Approach 2:
The patent creates a browser-compatible copy of the message display functionality by translating server-side Java message mechanisms into client-side JavaScript. This copied implementation runs in the browser environment and provides equivalent functionality without requiring the original Java platform, thus reducing device complexity requirements.
4Ease of manufacture
If JAVA script frameworks provide resource file mechanisms, then resource management is enabled, but multiple HTTP requests are generated for each resource bundle
Solution Approach 1:
The patent implements resource management by merging all resource files into a single bundled resource file. This approach enables easy resource management through a single file delivery mechanism while simultaneously eliminating the multiple HTTP requests that would otherwise be generated for each individual resource bundle.
Data Source
AI summary
Techniques for dynamic resource management are presented. A World-Wide Web (WWW) page is acquired on first access to a WWW site and rendered with a script tag. When a browser loads the WWW page, the script tag is processed to remotely execute a script on the WWW site. The script produces a single file having code for the resources that are referenced in the WWW page. The single file is provided back to the browser where it is cached so that when any of the resources are accessed via the WWW page, the needed code for those resources are available for execution within the cache of the browser.