Client-Side Callbacks for Partial Web Page Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Server-based Web applications experience long response times and unresponsive user experiences due to the need for full page postbacks, which involve submitting the entire form to the server, processing, and returning it, leading to inefficient processing power and extraneous navigation steps.
Innovation Solution
Implementing client-side callbacks to server events, where only the necessary server-side controls handle client-side events, reducing the need for full page postbacks and allowing partial processing, thus enabling efficient event handling and maintaining user interaction without unnecessary page refreshes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full page postbacks are used to handle client-side events, then server-based Web applications can maintain event handling on the server, but response time increases and user experience becomes unresponsive
Solution Approach 1:
The patent segments the Web page into multiple independent sections, allowing specific sections to be updated without requiring a full page postback. This enables partial page updates where only the affected section is submitted to the server and returned, significantly reducing response time while maintaining server-based event handling for segmented sections.
Solution Approach 2:
The patent extracts the event handling logic from the full page context and implements it at the section level. By taking out only the necessary section for processing rather than the entire page, the system reduces the amount of data transmitted and processed, thereby decreasing response time while preserving server-based event handling capabilities.
2Extent of automation
If full page postbacks are performed for every client event, then server controls can process events centrally, but processing power is wasted and navigation history becomes cluttered
Solution Approach 1:
The patent divides the Web page into multiple independent sections that can be processed separately. This segmentation allows the server to process only the specific section involved in the event rather than the entire page, eliminating wasted processing power while maintaining centralized event processing architecture.
Solution Approach 2:
The patent applies partial action by processing only the necessary section instead of the full page. This partial processing approach maintains the benefits of centralized server-based event handling while avoiding the excessive processing of unrelated page sections, thereby improving processing efficiency.
3Stability of the object's composition
If entire Web Forms are submitted and recreated for each event, then server-based controls can maintain state, but the user experience becomes distracting and non-responsive
Solution Approach 1:
The patent segments the Web form into multiple independent sections, allowing state to be maintained at the section level rather than requiring full form submission. This enables localized updates that preserve form state stability while providing responsive user experience through partial page updates.
Solution Approach 2:
The patent uses copying by creating and returning only the specific section that needs updating rather than copying the entire form. This selective copying approach maintains form state stability for the updated section while avoiding the disruption of full form recreation, thereby improving user experience responsiveness.
Data Source
AI summary
Described herein are systems and methods for client-side callbacks to server events in which a Web server receives a message indicating a client-side event. The client-side event is associated with a specific component of a client resource, the specific component being one of multiple static components of the client resource. A server-side component generates a response to the received message and implements at least a subset of logic of the specific component. In generating the response to the message, server-side logic corresponding to other static components that are different than the specific component are not used.