Unilateral web services interaction contract

• US 7,668,961 B2
• Filed: 09/23/2004
• Issued: 02/23/2010
• Est. Priority Date: 09/23/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lomet, David
• Primary Examiner(s): Winder; Patrice
• Assistant Examiner(s): Yu; Xiang
• Application Number:
  US10/947,707
• Publication Number:
  US 20060080670A1
• Time in Patent Office: 1,979 Days
• Field of Search: 709/218, 709/224, 714/15
• US Class Current: 709/230
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 11/1479 Generic software techniques for error detection or fault masking
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

The present invention leverages a unilaterally-based interaction contract that enables applications to have a persistent state and ensures an exactly-once execution despite failures between and by communicating entities, permitting disparate software applications to be robustly supported in an environment where little is known about the implementation of the interaction contract. In one instance of the present invention, a web services interaction contract provides a communicating application with duplicate commit request elimination, persistent state transitions, and/or unique persistent reply requests. The present invention permits this interaction contract to be supported by, for example, a persistent application, a workflow, a transaction queue, a database, and a file system to facilitate in providing idempotent executions for requests from a communicating application.

Claims

1. A system that facilitates persistent states, the system comprising:

a memory; and

a processor coupled to the memory, the processor executing components comprising;

an interaction component that interacts with at least one entity and unilaterally provides interaction information to facilitate recovery of the entity from a fault condition;

wherein the interaction information is based on, at least in part, a request received from the entity;

wherein the request includes a unique work item ID for tracking the request and enabling exactly-once execution of the request; and

wherein the interaction information is released based upon, at least in part, at least one process selected from a group consisting of a no release required process, a release encouraged process, and a release required process; and

a persistent state component that ensures that executions of requests of the entity result in persistent state changes and that messages to the entity are persistent, wherein the persistent state component is configured to ensure idempotent execution of the request by using the unique work item ID to ensure the request is executed exactly-once by performing acts comprising;

determining if the unique work item ID is being tracked in a message queue; and

determining if the unique work item ID is present in a request message or a reply message;

if the unique work item ID is present in a request message, cancelling the request, the request being a duplicate of a pending request; and

if the unique work item ID is present in a reply message, sending the reply message to the entity in response to the request, the request being a duplicate of a completed request.

2. The system of claim 1, the interaction component further provides the entity with at least one selected from the group consisting of duplicate commit request elimination, persistent state transitions, and unique persistent reply requests.

3. A web service component that employs the system of claim 1.

4. The system of claim 1, the entity resides, relative to the persistent state component, in a location that is at least one selected from the group consisting of local and remote.

5. The system of claim 1, the interaction component interacts with the entity via the World Wide Web.

6. The system of claim 1, the interaction component further employs at least one selected from the group consisting of a persistent application, a workflow, a transactional queue, a database, and a file system to facilitate in providing the interaction information.

7. The system of claim 1, the interaction component enables transparent state persistence for the entity.

8. The system of claim 1, the interaction component enables automatic recovery for the entity.

9. The system of claim 1, the entity comprising at least one selected from the group consisting of a software application, a web service, a client application, and a middle-tier application that is part of an application server.

10. The system of claim 1, the interaction component provides information for at least one persistent component (Pcom) based entity that enables crash recovery.

25. A computer readable storage medium having stored thereon computer executable components of the system of claim 1.

27. A device employing the system of claim 1 comprising at least one selected from the group consisting of a computer, a server, and a handheld electronic device.

11. A method for facilitating persistent states for entities, the method comprising:

interacting via a web service with at least one entity;

unilaterally determining, by a processor of the web service, interaction information based on, at least in part, a request received from the entity including a request for service and a request for cancellation of service;

wherein the processor is configured to execute a persistent system component which ensures idempotent execution of the request;

wherein the request includes a unique work item ID for tracking the request and enabling exactly-once execution of the request; and

wherein the interaction information is released based upon, at least in part, at least one process selected from a group consisting of a no release required process, a release encouraged process, and a release required process;

providing the interaction information to facilitate recovery of the entity from a fault condition;

determining if the unique work item ID is being tracked in a message queue; and

determining if the unique work item ID is present in a request message or a reply message;

if the unique work item ID is present in a request message, cancelling the request, the request being a duplicate of a pending request; and

if the unique work item ID is present in a reply message, sending the reply message to the entity in response to the request, the request being a duplicate of a completed request.

12. The method of claim 11 further comprising:

receiving a request from the entity;

checking a message queue for the presence of the request;

determining if a reply message is available in the message queue for the request;

waiting for the request to be processed and a reply message to be generated if the request is present in the message queue and the reply message is absent; and

sending the reply message to the entity if a reply message is present in the message queue.

13. The method of claim 11 further comprising:

receiving a cancel request with a unique work item ID from the entity;

determining if the unique work item ID exists in a message queue; and

canceling a request associated with the unique work item ID in the message queue if the ID is present in the message queue.

14. The method of claim 11, determining the interaction information comprising:

receiving a request with a unique work item ID from the entity;

determining if the unique work item ID exists in a work item database that contains a unique work item ID field for at least one work item in the database; and

entering the unique work item ID in the unique work item ID field associated with an appropriate work item if the unique work item ID is absent from the work item database.

15. The method of claim 14 further comprising:

retaining the unique work item ID with the work item for an entire time that the work item is relevant.

16. The method of claim 11 further comprising:

receiving a cancel request with a unique work item ID from the entity;

determining if the unique work item ID exists in a work item database that contains a unique work item ID field for at least one work item in the database; and

canceling a request associated with the unique work item ID in the work item database if the ID is present in the work item database.

17. The method of claim 11 further comprising:

providing the entity with at least one selected from the group consisting of duplicate commit request elimination, persistent state transitions, and unique persistent reply requests.

18. The method of claim 11 further comprising:

employing at least one selected from the group consisting of a persistent application, a workflow, a transactional queue, a database, and a file system to facilitate in providing the idempotent execution for the requests from the entity.

19. The method of claim 11 further comprising:

providing transparent state persistence for the entity.

20. The method of claim 11 further comprising:

providing an automatic recovery for the entity.

21. The method of claim 11, the entity comprising at least one selected from the group consisting of a software application, a web service, a client application, and a middle-tier application that is part of an application server.

22. The method of claim 11 further comprising:

providing crash recovery information for at least one persistent component (Pcom) based entity.

23. The method of claim 11 further comprising:

interacting with the entity via the Internet.

26. A device employing the method of claim 11 comprising at least one selected from the group consisting of a computer, a server, and a handheld electronic device.

24. A system that facilitates persistent states, comprising:

means for interacting with at least one entity; and

means for unilaterally providing interaction information to facilitate recovery of the entity from a fault condition including a system failure, an entity failure, and an application component failure;

the information based on, at least in part, requests received from the entity including a request for service and a request for cancellation of service;

means for storing the interaction information in a persistent state in accordance with a unilateral pledge, to the entity, to ensure idempotent execution of one or more requests from the entity;

means for releasing persistence of the information according to a release obligation in accordance with the unilateral pledge, the release obligation comprising;

no release required, wherein without instruction to the contrary, the interaction information is remains persistent;

release encouraged, wherein an incentive is provided to the entity to release the obligation to maintain persistence of the information;

release strongly encouraged, wherein denying service to the entity until the entity releases the obligation to maintain persistence of the information;

or

release required, wherein the obligation to maintain persistence of the information is released upon a subsequent contact with the entity or subsequent unilateral pledge to the entity.