Component Object Data Binding for Distributed Client-Server Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client-server computing paradigms face inefficiencies due to the need for different clients or client components to interface with various server applications, increasing the burden on both client and server devices, and limiting the ability to efficiently access and update data across remote devices.
Innovation Solution
A component object that declaratively binds business-driven services to a graphical user interface, using a data structure with a data model, view model, and controller to manage and present data, allowing for event handling and data binding between the client and server, while only exchanging necessary data to maintain the user interface state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different clients or client components are used to interface with different server applications, then data access capability is improved, but device complexity increases
Solution Approach 1:
The patent implements a universal data model that can represent data from multiple different server applications in a unified structure. This single data model serves multiple functions by adapting to different data sources through configuration rather than requiring separate client components for each server application, thereby reducing client complexity while maintaining data access capability.
Solution Approach 2:
The patent introduces an intermediary layer consisting of the unified data model and view model that sits between the client interface and the diverse server applications. This intermediary translates and standardizes data from different server formats into a common structure, allowing a single client to access multiple server applications without increasing client complexity.
2Adaptability or versatility
If different clients or client components are used to interface with different server applications, then data access capability is improved, but the burden on server increases
Solution Approach 1:
The patent enables the client side to perform self-service by implementing the unified data model and view model locally. The client independently handles data transformation, validation, and presentation logic without requiring the server to provide multiple specialized interfaces or perform complex data manipulation, thereby reducing the burden on the server while maintaining versatile data access.
3Power
If computationally intensive applications are run on server farms, then processing power is improved, but remote access capability is limited
Solution Approach 1:
The patent extracts the data representation and presentation logic from the server environment and places it in the client environment through the unified data model and view model. This allows the computationally intensive processing to remain on the server farm while the data access and presentation capabilities are extracted to the remote client devices, enabling easy remote access without compromising processing power.
4Ease of operation
If data exchange between client and server is increased to maintain UI state, then user interface responsiveness is improved, but data exchange optimization is reduced
Solution Approach 1:
The patent implements local quality by enabling the client to independently maintain UI state through the unified data model and view model. The client can locally determine what data needs to be exchanged based on current UI state and user context, rather than exchanging all data continuously. This optimizes data exchange by transmitting only necessary updates while maintaining responsive UI through local processing.
Data Source
AI summary
A component object binds business driven services to a graphical user interface (GUI). The object includes a data model, view model and controller. The view model graphically presents, and the controller manipulates data used by the object. The controller includes an event handler that respond to events generated within the GUI and binds data used by the object to a data source which can be another component object or a remotely located source. The event handler can call a local script to calculate the value of a data element within the object. The component object can be instantiated on a client, and can be configured to communicate with a corresponding component object on a server. The client and server component objects can exchange only that data that needs to be exchanged to maintain the current state of a user interface in the client computer.