Client GUI Object Rendering via Selective Data Scoping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In client-server based applications, the transfer of large amounts of data between client and server systems can strain communication links, especially when computationally intensive applications are run on servers and accessed on remote devices like smartphones or laptops, necessitating techniques to reduce data transfer without compromising utility.
Innovation Solution
A method and system for displaying objects in a graphical user interface where a lead selection and scoping information determine if a component object is viewable, and data fields are only retrieved from a server if needed, using declaratively marked entities and event handlers within the component object's data model to manage data scope and reduce unnecessary data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If large amounts of data are transferred between client and server, then the utility and completeness of the client-server architecture is maintained, but the communication link becomes strained and bandwidth is consumed
Solution Approach 1:
The patent extracts only the necessary data fields from the component object based on scoping information and lead selection criteria. The system determines which data fields are needed to render the component object in the graphical user interface and transfers only those specific fields from server to client, rather than transferring all available data.
Solution Approach 2:
The patent implements partial action by transferring a subset of data fields rather than the complete dataset. The system evaluates scoping information and lead selection to determine the minimum necessary data required for the current view, transferring only that partial amount needed to maintain utility while conserving bandwidth.
2Loss of information
If all data fields are transferred from server to client, then complete information is available for rendering, but data transfer volume increases and strains communication links
Solution Approach 1:
The system extracts only the necessary data fields from the complete dataset based on scoping information and lead selection. By evaluating which data fields are required for the current graphical view, the system transfers only those specific fields, maintaining information completeness for the current context while reducing overall data transfer volume.
Solution Approach 2:
The patent applies local quality by making data transfer decisions specific to each component object and its current view context. Rather than using a uniform approach for all data, the system evaluates scoping information and lead selection criteria locally for each data field determination, transferring data with quality appropriate to its specific rendering needs.
3Speed
If data is pre-loaded on the client, then access speed is improved, but unnecessary data is cached consuming memory and bandwidth
Solution Approach 1:
The system performs preliminary evaluation of scoping information and lead selection criteria before data transfer. By determining in advance which data fields are needed based on the current view context, the system prepares the exact data set required, avoiding both premature loading of unnecessary data and delays from on-demand retrieval.
Solution Approach 2:
The client system uses its own scoping information and lead selection criteria to determine what data is needed, rather than relying on the server to provide all data. This self-service approach allows the client to make intelligent decisions about data requirements based on its current state and user context.
Data Source
AI summary
Methods and apparatus for displaying objects in client GUI. A lead selection and scoping information is used to determine whether the object is viewable, and the object is rendered only if it is at least partially viewable. The lead selection and scoping information is used to determine whether data is needed to render the object, and data is received from a corresponding object on a server only if it is needed to render the object. Determining whether the object is viewable in the GUI can be based on declaratively marked entities within the object's view and on view calculation rules. Determining whether data is needed to render the object can be based on declaratively marked entities within the object's data model such as flags indicating whether the data field is valid or whether the binding of the data field to a data source is valid.