METHOD, SYSTEM AND PROGRAM PRODUCT FOR PROVIDING A STATUS OF A TRANSACTION WITH AN APPLICATION ON A SERVER

• US 20080215677A1
• Filed: 05/20/2008
• Published: 09/04/2008
• Est. Priority Date: 06/26/2003
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated
• Original Assignee: Michael J. Osias
• Inventors: Osias, Michael J.
• Granted Patent: US 9,152,962 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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 a request for a transaction on the server from a client;

invoking the application on the server to process the request;

generating a first code having a first Uniform Resource Locator (URL) that includes a first set of parameters, and sending the first code to the client, wherein the code indicates a source of a continuous periodic communication request; and

communicating the first URL from the client to the server to request 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 communicating step comprises communicating the first URL from the client to the server after expiration of the delay time.

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

5. The method of claim 2, further comprising:

generating, after the communicating 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 the second code to the client; and

communicating the second code to the server from the client after expiration of the delay time to request 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 communicating 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 communicating step if the transaction is complete.

9. A method for providing a status of a transaction with an application on a server, comprising:

receiving 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 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 code indicates a source of a continuous periodic communication request and wherein the first set of parameters comprises a delay time and a count, wherein the count counts the number of periodic communication requests;

sending the first code to the browser; and

communicating the first URL in the first code from the browser to a server agent on the server after expiration of the delay time to request the status of the transaction.

10. The method of claim 9, wherein the first URL is processed by the 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 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 the second code to the browser; and

communicating the second URL in the second code from the browser to the server 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:

a server agent for receiving a request for the transaction from a client, and for initiating the transaction based on the request;

a client code generator invoked by the server agent 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 code indicates a source of a continuous periodic communication request, and wherein the client communicates the first URL to the server agent 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.

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 after expiration of the delay time.

19. The system of claim 17, wherein the server agent processes the first URL to determine the status of the transaction, and invokes the client code generator 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 increments the count of the first set of parameters by one to yield the new count.

21. A program product stored on a recordable medium for providing a status of a transaction with an application on a server, which when executed, comprises:

agent program code configured to receive a request for the transaction from a client, and to initiate the transaction based on the request;

generator program code invoked by the agent program code configured 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 code indicates a source of a continuous periodic communication request and wherein the client communicates the first URL to the agent program code to request the status of the transaction.

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

23. The 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 agent program code after expiration of the delay time.

24. The program product of claim 22, wherein the agent program code is further configured to process the first URL to determine the status of the transaction, and to invoke the generator program 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.

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