Shared Worker Object Synchronizes Browser Tabs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for synchronizing data across multiple tabs of a web browser often result in a time lag, leading to unsynchronized data and potential user confusion.
Innovation Solution
The implementation of a shared worker object within a web browser that synchronizes data across tabs without relying on a web server, by communicating data requests and changes through a single shared worker that tracks previous requests and automatically updates relevant browsing contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data synchronization across multiple tabs is implemented through server-based communication, then data consistency is achieved, but time lag and user confusion occur due to delayed updates
Solution Approach 1:
The patent introduces a shared worker as an intermediary component that sits between multiple tabs and the server. This shared worker receives data from the server and distributes it to all connected tabs in real-time, eliminating the need for each tab to independently communicate with the server and reducing synchronization delays
Solution Approach 2:
The shared worker pre-establishes connection channels with all tabs before data arrives. When data is received from the server, the worker can immediately push updates to all connected tabs without establishing new connections, thus reducing time lag
2Adaptability or versatility
If multiple tabs independently communicate with the web server, then each tab can access data, but synchronization delays and user confusion result from lack of real-time updates
Solution Approach 1:
The patent merges the communication functionality of multiple independent tabs into a single shared worker. Instead of each tab independently communicating with the server, all tabs share a common worker that handles communication centrally, ensuring that all tabs receive identical data updates simultaneously while maintaining their independent browsing contexts
3Loss of time
If a shared worker tracks and distributes data updates across browsing contexts, then near-real-time synchronization is achieved, but system complexity increases
Solution Approach 1:
The shared worker is designed as a universal component that can serve multiple tabs from different browsing contexts simultaneously. It implements a standardized interface for receiving data from the server and distributing it to any number of connected tabs, reducing the need for separate synchronization mechanisms for each tab and thereby managing complexity
Data Source
AI summary
In an example embodiment, a shared worker object is used in a web browser to synchronize data across tabs in the web browser, without relying upon a web server to perform or coordinate that synchronization. More particularly, each browsing context includes a web page and zero or more web worker objects, each web worker object corresponding to a different module of the web page. The zero or more web worker objects in each web page user interface are then configured to communicate with a single shared worker, through which all data requests and data changes are sent. The single shared worker forwards data requests and data changes to the web server, but also tracks such data requests and then automatically updates any browsing context that requested a particular piece of data in the past with a change that occurred to that particular piece of data.