Providing a status of a transaction with an application on a server
First Claim
1. A method for providing a status of a transaction with an application on a server, comprising:
- receiving, by the server, a request for a transaction on the server from a client;
invoking the application on the server to process the request;
generating, by the server, a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, and sending, by the server, the first code to the client; and
receiving, by the server, the first URL from the client requesting the status of the transaction.
1 Assignment
0 Petitions
Accused Products
Abstract
Under the present invention, polling code is generated on a server and sent to a client in response to a transaction request received on the server from the client. The polling code includes a set of parameters such as a delay time and a polling count. After expiration of the delay time, the client will poll the server to request the status of the requested transaction. If the transaction is complete, the client will be redirected to a completion page. If the transaction is incomplete, and a polling count limit has not been reached, new polling code will be generated that includes the delay time and a new polling count. The new polling count is generated by incrementing the old polling count by one. The polling cycle is repeated until the transaction is complete, or the polling count limit is reached.
-
Citations
25 Claims
-
1. A method for providing a status of a transaction with an application on a server, comprising:
-
receiving, by the server, a request for a transaction on the server from a client; invoking the application on the server to process the request; generating, by the server, a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, and sending, by the server, the first code to the client; and receiving, by the server, the first URL from the client requesting the status of the transaction. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method for providing a status of a transaction with an application on a server, comprising:
-
receiving, by the server, a HTTP request for a transaction on the server from a browser on a client; invoking the application on the server to process the HTTP request; calling, by the server, a client code generator to generate a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, wherein the first set of parameters comprises a delay time and a count; sending, by the server, the first code to the browser; and receiving, by the server, the first URL in the first code from the browser after expiration of the delay time to process a request for the status of the transaction. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
15. A system for providing a status of a transaction with an application on a server, comprising:
-
server agent code stored in a memory and executable by a processing unit for receiving a request for the transaction from a client, and for initiating the transaction based on the request; client code generator code stored in the memory and invoked by the server agent code for generating a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, and for sending the first code to the client, wherein the client communicates the first URL to the server agent code to request the status of the transaction. - View Dependent Claims (16, 17, 18, 19, 20)
-
-
21. A computer program product for providing a status of a transaction with an application on a server, the computer program product comprising:
-
a non-transitory computer readable storage media; first program instructions to receive a request for the transaction from a client, and to initiate the transaction based on the request; second program instructions, invoked by the first program instructions, to generate a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, and to send the first code to the client, wherein the first program instructions receive the first URL from the client to process a request for the status of the transaction; and
whereinthe first and second program instructions are stored on the computer readable storage media. - View Dependent Claims (22, 23, 24, 25)
-
Specification