Transactional Session Management via Deep Copy Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Stateful applications face challenges in maintaining synchronized state across multiple layers and systems, making rollbacks difficult due to the direct manipulation of session data and lack of transactional support in existing session management concepts, leading to potential loss of session information during failures.
Innovation Solution
A system and method for transactional session management that creates a deep copy of session objects across all participating entities, allowing for rollback by supplying the deep copy to applications, ensuring session integrity and continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If stateful session management is used to maintain session data across requests, then session continuity and user experience are improved, but system complexity and difficulty of maintaining synchronized state across layers increase
Solution Approach 1:
The patent creates a copy of the session object at the beginning of each transactional unit of work. This copy serves as a snapshot that can be used for rollback operations, allowing the system to maintain session state while providing a mechanism to revert to previous states, thus reducing the complexity of managing session continuity across distributed layers.
Solution Approach 2:
The session object is copied in advance (at the beginning of the transactional unit of work) before any modifications occur. This preliminary action enables rollback capability without requiring complex transaction management during the actual session operations, simplifying the overall system architecture.
2Ease of operation
If direct manipulation of session data is allowed for ease of operation, then application development simplicity is improved, but ability to perform rollbacks and maintain transaction integrity deteriorates
Solution Approach 1:
By creating a copy of the session object at the start of each transactional unit of work, the patent enables both direct manipulation of session data during operations and the ability to rollback to the copied state if needed. This resolves the contradiction by providing both ease of operation and reliability.
Solution Approach 2:
The copied session object acts as an intermediary between the original session data and the rollback mechanism. Applications can directly manipulate the current session state while the copy serves as a safe backup, mediating between operational simplicity and transaction integrity.
3Adaptability or versatility
If session data is distributed across multiple layers and systems, then application architecture flexibility is improved, but difficulty of keeping state synchronized and maintaining consistency increases
Solution Approach 1:
The patent creates a local copy of the session object within each transactional unit of work, which can be manipulated independently without requiring immediate synchronization with other layers or systems. This copying mechanism maintains architecture flexibility while reducing the complexity of state synchronization across distributed components.
4Reliability
If deep copying of session objects is performed for all participating entities, then rollback reliability is improved, but memory consumption and processing overhead increase
Solution Approach 1:
The deep copy is performed in advance at the beginning of the transactional unit of work, before any modifications are made. This preliminary copying ensures that the copy captures the complete state of all participating entities, providing reliable rollback capability while concentrating the computational overhead at a specific point in time rather than continuously.
Solution Approach 2:
By performing deep copying of session objects for all participating entities, the patent ensures that a complete and accurate snapshot is created for rollback purposes. This approach prioritizes rollback reliability over memory efficiency, creating comprehensive copies that capture the full state of the system at the transaction boundary.
Data Source
AI summary
A system and method of transactional session management. Information sufficient to permit creation of a deep copy of a session object is saved concurrently for all aspects of the transaction. For example, the saving may save state information provided by different hierarchical levels of the session as well as possible different hardware or software entities participating in the session. In the event of a rollback condition, the deep copy is supplied to one or more applications. Those applications may then continue the session from the point of the deep copy.