Plug-in Cache Segmentation for Browser Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web browser caching systems are inefficient as they delete cached data when the cache size exceeds limits or when data is not accessed for a long time, leading to repeated network requests for previously accessed data, resulting in increased network traffic and slower loading times.
Innovation Solution
Implementing a plug-in cache that allows each plug-in to manage its own cache, intercept network requests, and update resources during idle periods, reducing the need for frequent network access and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a shared cache is used for multiple web pages, then the cache size can be utilized efficiently, but the cached data is deleted when the cache becomes too large or data is not accessed for a long time, leading to repeated network requests
Solution Approach 1:
The patent divides the shared cache into separate plug-in-specific cache segments. Each plug-in has its own dedicated cache space where data is retained even when the overall cache is full or idle time expires. This segmentation prevents the deletion of frequently used plug-in data while still allowing the shared cache to function for other purposes.
Solution Approach 2:
The system performs preliminary actions by pre-caching resources during idle periods before they are actually needed. The plug-in cache stores resources in advance during when the system is idle, so that when the plug-in needs to access these resources, they are already available locally, eliminating the need for time-consuming network requests.
2Reliability
If cached data is deleted to manage cache size, then the cache can maintain optimal performance, but network traffic increases as data must be重新 retrieved from remote servers
Solution Approach 1:
By segmenting the cache into plug-in-specific portions, the system maintains reliable cache performance for each plug-in independently. Even when the overall shared cache reaches capacity limits, the plug-in-specific cache segments preserve their data, preventing the need for network re-retrieval and reducing network traffic.
Solution Approach 2:
Each plug-in effectively serves itself by having dedicated cache space that autonomously retains its data without being subject to the shared cache's deletion policies. The plug-in cache self-manages its own data retention, ensuring that frequently accessed plug-in resources remain locally available without consuming shared cache resources that other applications need.
3Adaptability or versatility
If a shared cache is used across multiple web pages, then resource sharing is improved, but processor use increases due to managing cache deletion and re-retrieval operations
Solution Approach 1:
The cache is segmented into independent plug-in-specific portions, which reduces processor overhead for cache management. Each segment operates independently with its own retention policies, eliminating the need for complex centralized cache management decisions about what to delete and when, thereby reducing processor use while maintaining resource sharing capabilities.
Data Source
AI summary
An application may support the use of a plug-in. A plug-in may have an associated cache. The application may allow the plug-in to intercept network requests. The plug-in can determine if a network request is for an already-cached resource and provide the resource as a response to the intercepted network request. Additionally or alternatively, the application may allow the plug-in to make network requests. The plug-in can make a network request for data in order to add the data to the plug-in's cache. The plug-in may be able to determine when the application, the system, the network, or any suitable combination thereof are idle and cause cache requests to be made during idle periods.