Client-Server Page Navigation via Incremental Rendering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing page navigation techniques require a complete rewrite of web pages, leading to inefficiencies and issues with browser history navigation, as they do not effectively manage data transfer and incremental updates between pages.
Innovation Solution
Implementing a client-server computing architecture that uses minimal download features and page incremental rendering to package and transmit only the differences between pages, allowing for efficient navigation without rewriting entire pages, and utilizing a layer of indirection to control browser code execution and events during page transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If data compression and non-navigation operations are used to reduce data transfer, then data transfer is reduced, but a complete rewrite of the web page is required and page changes are not recorded in browser history
Solution Approach 1:
The patent segments the web page into multiple independent parts or components, allowing only the changed portions to be transmitted and applied to the client, rather than rewriting the entire page. This segmentation enables partial page updates while maintaining browser history functionality.
Solution Approach 2:
The patent implements preliminary action by pre-processing and packaging the incremental changes on the server side before transmission. The server prepares the differential data in advance, so that when navigation occurs, only the necessary incremental updates are sent to the client, reducing data transfer while maintaining navigation reliability.
2Loss of energy
If data compression and non-navigation operations are used to reduce data transfer, then data transfer is reduced, but each individual part of a page may update separately which is expensive and inefficient
Solution Approach 1:
The patent merges multiple incremental updates into a single packaged differential that can be applied atomically. By combining the changes and transmitting them as a unified package, the system avoids the inefficiency of separate updates while still reducing overall data transfer compared to complete page rewrites.
3Reliability
If complete page rewrite is performed during navigation, then browser history navigation operates correctly, but the amount of data sent to the web page is large
Solution Approach 1:
The patent segments the web page into multiple independent parts or components, allowing only the changed portions to be transmitted and applied to the client, rather than rewriting the entire page. This segmentation enables partial page updates while maintaining browser history functionality.
4Loss of energy
If incremental updates are applied separately to each part of the page, then data transfer is reduced, but the update process becomes expensive and inefficient
Solution Approach 1:
The patent merges multiple incremental updates into a single packaged differential that can be applied atomically. By combining the changes and transmitting them as a unified package, the system avoids the inefficiency of separate updates while still reducing overall data transfer compared to complete page rewrites.
Data Source
AI summary
Embodiments are provided that include client-server computing architectures that use minimal download features and functionality as part of page navigation operations, but are not so limited. In an embodiment, a client-server computer system uses a page transition strategy to navigate between electronic pages based in part on script, style, content, and/or other page differences that can be used as part of providing minimal download features and functionality. A method of an embodiment operates to package page incremental rendering information for use in rendering a new electronic page without having to reapply common aspects of the new electronic page and a reference electronic page. Other embodiments are also disclosed.