Providing a status of a transaction with an application on a server

• US 9,152,962 B2
• Filed: 05/20/2008
• Issued: 10/06/2015
• Est. Priority Date: 06/26/2003
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Osias, Michael J.
• Primary Examiner(s): Nguyen, Thuong
• Application Number:
  US12/118,485
• Publication Number:
  US 20080215677A1
• Time in Patent Office: 2,695 Days
• Field of Search: 709/203, 709/224, 709/231, 709/218, 725/16, 710/267, 705/26
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

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.

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.

2. The method of claim 1, wherein the first set of parameters comprises a delay time and a count.

3. The method of claim 2, wherein the receiving of the first URL step comprises receiving the first URL from the client after expiration of the delay time.

4. The method of claim 2, wherein the receiving of the first URL step further comprises receiving, by a server agent on the server, the first URL from a browser on the client after expiration of the delay time, and wherein the server agent determines the status of the transaction based on the first URL.

5. The method of claim 2, further comprising:

generating, by the server after the receiving of the first URL step, a second code having a second URL that identifies a second set of parameters if the transaction is incomplete and the count does not equal a count limit;

sending, by the server, the second code to the client; and

receiving, by the server, the second code from the client after expiration of the delay time to process a request for the status of the transaction.

6. The method of claim 5, wherein the generating step comprises incrementing the count of the first set of parameters by one to yield a new count.

7. The method of claim 2, further comprising directing the client to an exception page after the receiving of the first URL step if the count equals a count limit and the transaction is incomplete.

8. The method of claim 2, further comprising directing the client to a completion page after the receiving of the first URL step if the transaction is complete.

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.

10. The method of claim 9, wherein the first URL is processed by a server agent on the server to determine the status of the transaction.

11. The method of claim 9, further comprising directing the browser to a completion page if the transaction is complete.

12. The method of claim 9, further comprising directing the browser to an exception page if the transaction is incomplete and the count equals a count limit.

13. The method of claim 9, further comprising generating, by the server, a second code having a second Uniform Resource Locator (URL) that identifies a second set of parameters and the transaction requested if the transaction is incomplete and the count does not equal a count limit, wherein the second set of parameters comprises the delay time and a new count.

14. The method of claim 13, further comprising:

sending, by the server, the second code to the browser; and

receiving, by the server, the second URL in the second code from the browser after expiration of the delay time to request the status of the transaction.

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.

16. The system of claim 15, wherein the client comprises a browser for receiving the first code, and for communicating the first URL to the server agent code.

17. The system of claim 15, wherein the first set of parameters includes a delay time and a count.

18. The system of claim 17, wherein the client communicates the first URL to the server agent code after expiration of the delay time.

19. The system of claim 17, wherein the server agent code processes the first URL to determine the status of the transaction, and invokes the client code generator code to generate a second code having a second URL that identifies a second set of parameters if the transaction is incomplete and the count does not equal a count limit.

20. The system of claim 19, wherein the second set of parameters comprises the delay time and a new count, and wherein the client code generator code increments the count of the first set of parameters by one to yield the new count.

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

wherein

the first and second program instructions are stored on the computer readable storage media.

22. The computer program product of claim 21, wherein the first set of parameters includes a delay time and a count.

23. The computer program product of claim 22, wherein the client comprises a browser configured to receive the first code, and to communicate the first URL to the first program instructions after expiration of the delay time.

24. The computer program product of claim 22, wherein the first program instructions are further configured to process the first URL to determine the status of the transaction, and to invoke the second program instructions to generate a second code having a second URL that identifies a second set of parameters if the transaction is incomplete and the count does not equal a count limit.

25. The computer program product of claim 24, wherein the second set of parameters comprises the delay time and a new count, and wherein the second program instructions increments the count of the first set of parameters by one to yield the new count.