Client-Side Scripting Object Cloning for Portal State Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for preserving client-side state information in client-server environments often require sending object state information to the server for every user interaction, leading to performance costs, increased communication traffic, and higher server memory and resource requirements.
Innovation Solution
Implementing client-side state-preservation systems that store scripting objects, such as JavaScript objects, in shared memory, allowing for cloning and retention of state information during document reloads, thereby reducing the need for server involvement and improving system performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If server-side caching is used to preserve client state information, then state information can be maintained during document reloads, but performance costs increase due to serialization of scripting objects to stream
Solution Approach 1:
The patent creates a copy of the scripting object in the portal page namespace, allowing the object to be retained during document reloads without requiring server-side serialization. This copying approach preserves state information while avoiding the performance costs of server communication and object serialization.
2Reliability
If server-side caching is used to preserve client state information, then state information can be maintained during document reloads, but communication traffic increases
Solution Approach 1:
The patent extracts the state preservation mechanism from the server and implements it client-side by creating a copy of the scripting object in the portal page namespace. This eliminates the need for continuous server communication and object serialization, thereby reducing communication traffic while maintaining state information.
3Reliability
If server-side caching is used to preserve client state information, then state information can be maintained during document reloads, but server memory and resource requirements increase
Solution Approach 1:
The patent moves the state preservation functionality from the server to the client by creating a copy of the scripting object in the portal page namespace. This extraction eliminates the need for server memory allocation and resource management for state preservation, reducing server memory requirements while maintaining state information during document reloads.
4Reliability
If server-side caching is used to preserve client state information, then state information can be maintained during document reloads, but device complexity increases
Solution Approach 1:
The patent implements self-service by creating a copy of the scripting object in the portal page namespace, allowing the client to autonomously preserve its own state information during document reloads. This eliminates the need for complex server-side state management mechanisms, reducing device complexity while maintaining state information.
Data Source
AI summary
Systems and techniques to preserve state information in a client-server environment. In general, in one implementation, the technique includes: storing, in a shared memory of a client, a scripting object that retains state information for an original document, and cloning the stored scripting object to a newly loaded document. Storing the scripting object can involve copying a scripting object reference to the shared memory to cause retention of the scripting object by the client during document loading. Cloning the stored scripting object to the newly loaded document can be performed recursively, and can involve creating a new scripting object in the new document and copying data from the stored scripting object to the new scripting object. The state information retained in the scripting object can be navigation information associated with the loaded document, and the loaded document can be a portal page in a portal system.