Multi-Page Flow Control Using Session History and Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for flow control between a browser and a server, such as using tokens, fail to prevent unauthorized processing of pages and do not effectively manage multiple frames, leading to potential double processing and flow errors.
Innovation Solution
Implementing a method that uses a request identifier and a business process identifier, stored in memory, to restrict page processing to the intended flow, and maintaining a session history to recover from flow errors without restarting the program, including the use of unique character strings and event identifiers to manage page flow across multiple frames.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a token is used to control page flow between browser and server, then flow control is improved, but the system becomes vulnerable to double processing when users navigate back or refresh pages
Solution Approach 1:
The patent divides the flow control mechanism into two separate components: a token (for page identification) and a transaction identifier (for processing control). This segmentation allows the token to be rewritten on page navigation while the transaction identifier maintains unique processing control, preventing double processing while enabling flexible page navigation.
Solution Approach 2:
The transaction identifier acts as an intermediary between the token and the processing control. It is embedded with the token but provides an additional layer of control that prevents duplicate processing even when the token is rewritten during browser navigation history operations.
2Ease of operation
If the token is rewritten when browser receives Back or Refresh instruction, then page flow continuity is improved, but processing may be run twice causing data mismatch
Solution Approach 1:
By separating the token (which can be rewritten for continuity) from the transaction identifier (which maintains unique processing control), the system allows smooth page navigation while preventing duplicate processing. The transaction identifier ensures that even if the token is rewritten, the processing control remains accurate.
Solution Approach 2:
The transaction identifier is embedded with the token before the page is sent to the browser. This preliminary action ensures that the processing control is established in advance and cannot be compromised by subsequent token rewriting operations during browser navigation.
3Device complexity
If a single token is used for multiple frames, then device complexity is reduced, but the system cannot distinguish between multiple frames processing different pages
Solution Approach 1:
The patent segments the flow control information into the token (for page identification) and the transaction identifier (for processing control). This segmentation enables the system to distinguish between multiple frames processing different pages while maintaining a relatively simple overall structure, as the transaction identifier is embedded with each token.
Solution Approach 2:
The transaction identifier adds another dimension to the flow control mechanism. Instead of relying solely on the token which can be rewritten, the transaction identifier provides an additional layer of identification that persists across frame navigation, enabling the system to distinguish between multiple frames without significantly increasing complexity.
Data Source
AI summary
A method and system are provided for maintaining flow control in a multi-page process. Each page that is produced by a server is embedded with an identifier. Similarly, each event that is processed by a browser is embedded with an event identifier. Both of these identifiers are stored in a session history. When a page is processed out-of-order from the intended flow, the session history is consulted to determine if a recovery of the flow can be maintained, or if the browser must return to the beginning of the program.