Web Page Data Persistence via Object Serialization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional web pages lack the ability to efficiently persist complex data objects between pages, requiring regeneration of web pages and storage of data on servers, which limits the reuse of features and data objects.
Innovation Solution
A system where a server receives user inputs and object-related data from a first web page, reconstructs object instances, and generates rendering data for a second web page, allowing object-related data to persist without server storage, enabling efficient posting between web pages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional HTML forms are used to post data between web pages, then data can be submitted to a server, but complex objects cannot be properly represented and the target page must be completely regenerated
Solution Approach 1:
The patent uses serialization to create a copy of the object state that can be transmitted as text. The object's properties are copied into a serialized format that preserves the data structure while enabling transmission through standard HTTP protocols, avoiding the need to regenerate the entire target page.
Solution Approach 2:
The patent transforms complex object data into a serialized parameter format that can be included in URL queries or form submissions. By changing the representation of object data from binary/memory-based to text-based parameters, the system enables transmission of complex objects through traditional web forms while maintaining the ability to reuse target pages.
2Reliability
If data is stored on the server for each web page to enable data persistence, then data can be maintained between pages, but server storage requirements increase
Solution Approach 1:
The patent extracts the essential object state information and transmits it client-side through URL parameters or hidden form fields. By taking out only the necessary data representation and moving it to the client side, the system achieves data persistence without requiring server-side storage for each page's data state.
Solution Approach 2:
The patent uses URL parameters and form fields as intermediaries to carry object state data between pages. These intermediaries transfer the serialized object information from the source page to the target page without requiring permanent server storage, enabling temporary data persistence through the request-response cycle.
3Adaptability or versatility
If the target web page is regenerated for each post request to use submitted values, then custom data can be displayed, but processing time increases
Solution Approach 1:
The patent performs preliminary serialization of object data on the source page before submission. By preparing the data in a transmittable format in advance and including it in the request, the target page can directly use the submitted values without requiring extensive regeneration or reparsing operations, reducing processing time.
4Ease of operation
If only actual values are posted to the server as text strings, then data can be transmitted, but the ability to send complex objects is lost
Solution Approach 1:
The patent uses serialization to create a copy of the object state that can be transmitted as text. The object's properties are copied into a serialized format that preserves the data structure while enabling transmission through standard HTTP protocols, avoiding the need to regenerate the entire target page.
Solution Approach 2:
The patent transforms complex object data into a serialized parameter format that can be included in URL queries or form submissions. By changing the representation of object data from binary/memory-based to text-based parameters, the system enables transmission of complex objects through traditional web forms while maintaining the ability to reuse target pages.
Data Source
AI summary
The described systems and methods are directed at persisting data between web pages. A server receives object-related data associated with a first web page and a request for posting to a second web page from a client. The object-related data includes information about the objects in the first web page. Instances of the objects associated with the first web page are reconstructed based, at least in part, on the object-related data. The server generates rendering data of the second web page based, at least in part, on the reconstructed object instances. In this manner, the object-related data is allowed to persist from the first web page to the second web page.