Server Session Tracking for Duplicate Request Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computer networks, particularly over the Internet, there is a risk of double processing of requests due to repeated submissions by users, which can lead to unintended processing of requests, such as double booking in transactional systems, especially when users refresh or re-submit requests before receiving responses.
Innovation Solution
A server-side method that prevents double processing by recognizing repeated requests and assigning prepared response data to them, ensuring that only the initial request's response is processed, thereby avoiding duplicate processing through the use of session identifiers and mobile program code to manage and display status updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server returns an intermediate web page requesting the user to be patient and refrain from refreshing or resubmitting, then double processing is prevented, but user experience deteriorates due to manual constraints and potential confusion
Solution Approach 1:
The system automatically detects repeated requests and handles them without requiring user intervention. The server monitors incoming requests, identifies duplicates through session tracking, and automatically serves cached responses, eliminating the need for users to follow manual instructions to avoid double processing.
Solution Approach 2:
An intermediate response caching mechanism is introduced between the request processing and response delivery. When a repeated request is detected, the system retrieves the cached response from the previous processing attempt and delivers it directly, acting as a mediator that prevents duplicate processing without user awareness.
2Device complexity
If the server processes each request independently without tracking, then system complexity is reduced, but data integrity deteriorates due to potential duplicate processing
Solution Approach 1:
The server performs preliminary tracking of processed requests using session identifiers before actual processing completes. By recording the session ID and request state in advance, the system can quickly identify and filter duplicate requests without adding complex processing logic during the main transaction flow.
Solution Approach 2:
The system creates a cached copy of the response data from the first request processing and reuses it for subsequent repeated requests. This copying mechanism maintains data integrity by ensuring identical responses are returned without requiring re-processing, thus preserving reliability while maintaining simple processing logic.
3Reliability
If session identifiers are used to track and identify repeated requests, then double processing is prevented, but system complexity increases due to session management overhead
Solution Approach 1:
The session identifier mechanism serves multiple functions simultaneously: it tracks user state, identifies repeated requests, and enables response caching. By making the session ID multi-functional, the system prevents double processing without requiring separate tracking systems, thus reducing overall complexity while maintaining reliability.
4Loss of time
If the server caches and reuses response data for repeated requests, then processing time is reduced, but memory usage increases due to cached data storage
Solution Approach 1:
The response caching is implemented locally within the server's memory space, utilizing available resources efficiently. By caching responses at the server level rather than distributing cache across multiple components or external systems, the approach minimizes overall system complexity and memory overhead while achieving fast response times for repeated requests.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and computer programs for preventing double processing of a repeated request from a client in a transaction session are provided. A first request is received from the client over the computer network and processed. When a repeated request is received from the client, response data prepared in response to the first request are assigned to the repeated request. A response to the repeated request is returned to the client comprising the response data prepared in response to the first request.