Protecting in-flight transaction requests
AssigneeInternational Business Machines Corporation
InventorsJose E. Garza, Stephen J. Hobson
Life of this patent
Estimating the term…
Abstract
The subject matter described herein relates to protecting in-flight transaction requests, where a client device is connected via at least two application servers to a backend server device that is capable of processing redundant transaction requests originated by the client device. A first instance of a transaction request identified by a transaction identifier is received at the backend server device. The first instance of the transaction request is processed and a transaction response is sent to the client device. The transaction response identified by the transaction identifier is saved in a cache. If a subsequent instance of the transaction request is received, the cached transaction response is sent to the client device.
Claims20
A computer-implemented method for protecting in-flight transaction requests, the method carried out at a backend computing server, comprising:
- by a processor of a backend server device capable of processing redundant transaction requests, originated by a client device, that are received via one or more of at least two application servers:
- receiving a first instance of a transaction request identified by a transaction identifier;
- processing the first instance of the transaction request and sending a transaction response to the client device;
- saving the transaction response identified by the transaction identifier in a cache;
- and
- if a subsequent instance of the transaction request is received, sending the cached transaction response to the client device.
A computer-implemented method for protecting in-flight transaction requests, the method carried out at a computing client comprising:
- by a processor of a client device connected via at least two application servers to a backend server device:
- sending two or more identical redundant instances of a transaction request, each comprising a same transaction identifier, with each instance of the transaction request being sent via a different one of the at least two application servers;
- receiving a first instance of a transaction response identified by the transaction identifier;
- saving the first instance of the transaction response identified by the transaction identifier or a record of the first instance of the transaction response identified by the transaction identifier in a cache;
- and
- if a subsequent instance of the transaction response is received, deleting the received subsequent instance of the transaction response.
A system for protecting in-flight transaction requests at a backend computing server comprising:
- a cache;
- and
- a processor of a backend server device capable of processing redundant transaction requests, originated by a client device, that are received via one or more of at least two application servers, where the processor is programmed to:
- receive a first instance of a transaction request identified by a transaction identifier;
- process the first instance of the transaction request and send a transaction response to the client device;
- save the transaction response identified by the transaction identifier in the cache;
- and
- if a subsequent instance of the transaction request is received, send the cached transaction response to the client device.
Dependencies are inferred from the claim text.