Session Sharing Shared Worker Module for Browser Network Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web browser implementations suffer from poor system performance and increased power consumption due to the need for multiple individual connection ports when multiple tabs are open, leading to delayed server responses, slow webpage load times, and network congestion.
Innovation Solution
Implementing a session sharing shared worker application that creates a single connection port for multiple tabs, allowing requests from different tabs to be combined and routed through a shared worker space, reducing the need for individual connections and optimizing network communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple individual connection ports are created for each tab to connect to the server, then each tab can independently communicate with the server, but network communication efficiency deteriorates and power consumption increases
Solution Approach 1:
The patent merges multiple individual connection ports into a single shared connection port that serves multiple tabs. The worker module establishes one connection to the server and manages communication for multiple tabs, eliminating the need for each tab to maintain its own separate connection. This combining approach resolves the contradiction by maintaining reliable communication capability while significantly improving network efficiency and reducing power consumption.
Solution Approach 2:
The worker module is designed with multi-functionality, serving as a universal communication handler for multiple tabs simultaneously. Instead of dedicating a single connection port to one tab, the worker module can manage connections and data exchange for multiple tabs through its single connection port, making the connection resource universal and applicable to multiple tabs.
2Ease of operation
If multiple individual connection ports are created for each tab, then direct server communication is enabled, but system performance deteriorates due to network congestion and delayed responses
Solution Approach 1:
The worker module acts as an intermediary between multiple tabs and the server. Instead of tabs directly communicating with the server through individual connection ports, the worker module mediates all communication by establishing a single connection to the server and managing data exchange on behalf of multiple tabs. This intermediary approach maintains ease of operation while eliminating network congestion and improving system performance.
3Productivity
If a single connection port is shared among multiple tabs, then network communication efficiency improves and power consumption reduces, but data routing complexity increases
Solution Approach 1:
The worker module implements feedback mechanisms to track and manage communication states for multiple tabs. By monitoring which tabs are active, which connections are established, and routing data back to the appropriate tabs based on feedback information, the system manages the single connection port efficiently. This feedback approach handles the routing complexity systematically while maintaining high network communication efficiency.
Data Source
AI summary
Various methods, apparatuses, and media for implementing a session sharing shared worker module are provided. A processor executes a first web application and a second web application within a web browser. The first web application is associated with a first tab and the second web application is associated with a second tab having different web content than the first tab. The processor determines whether a shared worker is available within the web browser. A session sharing module is configured to: register each of the first tab and the second tab with the shared worker based on determining that the shared worker is available within the web browser; receive a first request from the first tab to connect to a server and a second request from the second tab to connect to the server; combine the first request and the second request into one packaged request; and send the one packaged request to the server via one connection point.