Wire Web Component Graph for Dynamic Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing HTML-based user interfaces for accessing data in database systems lack efficient mechanisms for dynamic updating of data, leading to inconsistencies and inefficiencies in data synchronization across different parts of the user interface.
Innovation Solution
The implementation of wire web components and a wire web component graph that allows for dynamic updating of data in user interfaces. This involves identifying predicted wire web components, constructing a graph that links components to data fields and APIs, and transmitting GUI messages with retrieved data values to client machines for real-time updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional HTML-based user interfaces are used for accessing data in database systems, then the system is simple to implement, but data synchronization across different parts of the user interface becomes inconsistent and inefficient
Solution Approach 1:
The user interface is segmented into independent wire web components, each representing a discrete data access point. Each component is associated with specific data fields and APIs, allowing independent management and updating of data bindings without affecting the entire interface. This segmentation enables consistent data synchronization across distributed interface elements.
Solution Approach 2:
The patent implements a nested hierarchical structure where wire web components are linked to data fields, which are in turn linked to APIs and data object instances. This nested architecture (components → fields → APIs → data objects) creates a structured dependency chain that maintains data consistency while allowing granular control at each level of the hierarchy.
2Productivity
If manual data updating mechanisms are used in user interfaces, then the implementation is straightforward, but dynamic updates lead to race conditions and data inconsistencies
Solution Approach 1:
The wire web component graph establishes feedback mechanisms where components automatically detect changes in their associated data fields and trigger appropriate updates. When data object instances change, the system propagates these changes through the graph structure, ensuring all dependent components receive synchronized updates without manual intervention or race conditions.
Solution Approach 2:
The system pre-establishes the wire web component graph structure and data bindings before runtime operations. By pre-defining the relationships between components, fields, and APIs, the system prepares the data flow pathways in advance, enabling automatic and consistent updates when data changes occur, rather than manually managing updates during execution.
3Loss of information
If comprehensive data fetching from multiple APIs is performed, then complete data availability is achieved, but the amount of data transferred and processing overhead increases
Solution Approach 1:
The patent extracts and retrieves only the specific data fields that are actually bound to wire web components in the user interface. Rather than fetching complete data sets from APIs, the system identifies and retrieves only the necessary data objects and fields required by the interface, reducing data transfer volume while maintaining completeness of displayed information.
Solution Approach 2:
The system implements partial data fetching by retrieving only the subset of data required by the user interface components. The wire web component graph enables selective data access, fetching data from APIs only for the specific fields that are currently bound and displayed, avoiding unnecessary data transfer and processing overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A wire web component graph that includes a plurality of nodes may be accessed to identify one or more application procedure interfaces (APIs) through which to update one or more data values included in a designated wire web component in a graphical user interface (GUI) being presented on a display device. Each of the data values may correspond to a respective data field represented in the wire web component graph, and each data field may be associated with a respective API in the wire web component graph. The graphical user interface may be updated based on one or more updated data values determined by communicating with the identified APIs over a network and via a communications interface.