Delta Rendering for Web Page Event Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web-based applications, such as Business Server Page (BSP) applications, face limitations in interactivity due to the need for roundtrip communication between the client and server for event handling, leading to sluggish performance and wasteful use of processor and network bandwidth, as they often require rendering of entire HTML pages even when only a portion needs updating.
Innovation Solution
Implementing delta rendering, where only the portion of presentation code correlated to a triggering object is updated, using Asynchronous JavaScript and XML (AJAX) to enable asynchronous, non-blocking transactions and reduce the payload sent between the client and server, allowing for more interactive and responsive user interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous HTTP transactions are used for event handling, then data integrity is ensured, but application responsiveness deteriorates due to blocking nature
Solution Approach 1:
The patent applies dynamics by transitioning from static synchronous HTTP transactions to dynamic asynchronous XML-based communication. The system dynamically adapts the communication mode based on event type, allowing simultaneous multiple transactions without blocking, thereby improving responsiveness while maintaining data integrity through structured XML data exchange.
2Reliability
If complete BSP tree rendering is performed for every client event, then all possible update areas are covered, but processor bandwidth is wasted on unnecessary rendering
Solution Approach 1:
The patent segments the complete BSP tree rendering process into selective area rendering. Instead of rendering the entire BSP tree for every event, the system identifies and renders only the specific target areas affected by the triggering event. This segmentation is achieved through event-object-area mapping that divides the rendering workload into discrete, manageable segments corresponding to actual update needs.
Solution Approach 2:
The patent applies local quality by making different parts of the rendering process have different processing intensities. High-quality complete rendering is applied only when necessary (full page updates), while localized selective rendering is applied for specific event types. This ensures update completeness for critical areas while reducing processor bandwidth consumption for less critical updates.
3Reliability
If complete HTML pages are transmitted for every event, then all update information is provided, but network bandwidth is wasted on unnecessary data transmission
Solution Approach 1:
The patent extracts only the necessary portions of HTML content from complete page transmissions. Instead of sending entire HTML pages for every event, the system identifies and extracts only the specific HTML fragments corresponding to target areas that need updating. This extraction is based on the mapping between triggering objects and their associated target areas, eliminating unnecessary data transmission while ensuring all required update information is provided.
4Reliability
If traditional event handling with full page rendering is used, then all areas are updated, but interactivity is limited due to sequential processing
Solution Approach 1:
The patent enhances interactivity by dynamically enabling simultaneous multiple XML transactions through asynchronous processing. Unlike traditional sequential HTTP transactions, the system allows multiple events to be processed concurrently without blocking, significantly improving productivity and user interactivity while maintaining update accuracy through structured XML data exchange and selective area rendering.
Data Source
AI summary
A method and apparatus for reducing network and processor bandwidth overhead when a client device fetches a Web page from a server. Presentation code is provided to mark view identifiers as well as indicate target areas of the Web page to be updated upon occurrence of selected events. The presentation code is further marked to indicate the target areas. Upon an event at the client the associated view identifier is located as well as the target areas for the event retrieved utilizing the marking information. Only the selected target areas are updated on the current Web page. A server-side optimization causes only the target areas to be rendered upon a request for the Web page.