Partial Client Interface Updates via Middleware Queues
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional client-server models, particularly in Web-based applications, require whole page refreshing to manage state changes, which is inefficient for interactive applications where only specific elements need updating, leading to waste and visual annoyance.
Innovation Solution
Implementing a method for partial updating of client interfaces by tracking state changes in multiple interface elements and applying changes only to affected elements, using a middleware engine that communicates state changes across stateless protocols like HTTP, allowing for dynamic and seamless updates without refreshing entire container structures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If whole page refreshing is used to update client interface, then state changes are accurately reflected, but unnecessary updates and visual annoyance occur
Solution Approach 1:
The patent segments the interface container into multiple independent interface elements, each capable of being updated individually. Instead of refreshing the entire page, only the specific elements that have changed state are updated, eliminating visual annoyance while maintaining accuracy of state changes.
Solution Approach 2:
The patent applies local quality by tracking state changes at the element level rather than globally. Each interface element maintains its own state information, allowing the system to identify and update only those elements whose state has changed, avoiding unnecessary updates to unchanged elements.
2Reliability
If whole page refreshing is used to update client interface, then complete interface state is synchronized, but network bandwidth and processing time are wasted
Solution Approach 1:
The patent extracts only the changed state information from the server and transmits it to the client, rather than transmitting the entire interface container. This extraction of minimal necessary data reduces network bandwidth consumption while maintaining synchronization of interface state.
Solution Approach 2:
The patent applies partial action by performing only the necessary updates to changed elements rather than completely regenerating and transmitting the entire interface. This partial updating approach maintains synchronization reliability while minimizing network bandwidth usage and processing time.
3Stability of the object's composition
If whole page refreshing is used to update client interface, then interface consistency is maintained, but user interaction responsiveness is reduced
Solution Approach 1:
The patent introduces dynamics by enabling asynchronous, incremental updates of interface elements as their state changes, rather than forcing synchronous full-page refreshes. This allows the interface to remain consistent while responding dynamically to user interactions without interruption or visual disruption.
Data Source
AI summary
A method and apparatus for partial updating of client interfaces in a client-server environment. The client updates the corresponding server-side through a middleware “engine.” Individual interface element change requests may be queued. Programmatically defined events may trigger processing of the change request queue on the client, resulting in partial updating of an interface container, such as a Web page or XML document, in the client interface context. Processing may occur on the server, where resultant client update requests are likewise queued. Alternative programmatically defined events may trigger the return of the server change queue to the client. Only those elements of the interface container affected by changes in the queue are updated. This partial updating method replaces the need for refreshing an entire interface, thus affording a more desktop-like look and feel.