Web service application protocol and SOAP processing model
First Claim
1. In a computing environment, a method comprising:
- determining that a web service provided by a web services provider provides a plurality of different behaviors, the web service being identified by a unique web service identifier, wherein each web service behavior is provided by a different logical entity and wherein each web service defines which requests it is configured to receive and in which order it is configured to receive the requests;
assigning a separate data communication port to each of the plurality of different web service behaviors, the assigned data communication port being different than the web service identifier, wherein the data communication port allows a client to individually address and access the logical entities that provide each of the different web service behaviors separately, without addressing the web service identifier, and wherein the data communication ports maintain a list of ports including interaction between the ports, which provides an observable directory of what web service operations have occurred and in what order the operations occurred;
receiving a client request that requests web service functionality which utilizes at least two of the web service'"'"'s behaviors; and
returning assigned unique identifiers for each of the at least two web service behaviors in response to the client request, to allow the client to access each behavior separately using each behavior'"'"'s assigned data communication port, wherein, based on the client request and based on the observable directory of what web service operations have occurred and in what order the operations occurred, multiple web services are run simultaneously in parallel.
2 Assignments
0 Petitions
Accused Products
Abstract
Described is a Web Services Application Protocol (WSAP) comprising a SOAP-based protocol that defines a web service application model based on a set of common message operations. WSAP provides a foundation for defining web services in terms of how they interact with each other. In WSAP, the behaviors of a service are each provided with an individual port, (e.g., URI), whereby the service'"'"'s behaviors may be interacted with directly. WSAP also defines shared semantics for operations that identify what a message is, what the processing of message is, and how it affects the state/behavior of the receiver. The ordering of messages also provides context to what is occurring. As a result of the known characteristics of the operations and the ordering, an intermediary can process exchanged messages to add value to communications. A SOAP processing model defines composing multiple web services to run in parallel or sequentially.
23 Citations
30 Claims
-
1. In a computing environment, a method comprising:
-
determining that a web service provided by a web services provider provides a plurality of different behaviors, the web service being identified by a unique web service identifier, wherein each web service behavior is provided by a different logical entity and wherein each web service defines which requests it is configured to receive and in which order it is configured to receive the requests; assigning a separate data communication port to each of the plurality of different web service behaviors, the assigned data communication port being different than the web service identifier, wherein the data communication port allows a client to individually address and access the logical entities that provide each of the different web service behaviors separately, without addressing the web service identifier, and wherein the data communication ports maintain a list of ports including interaction between the ports, which provides an observable directory of what web service operations have occurred and in what order the operations occurred; receiving a client request that requests web service functionality which utilizes at least two of the web service'"'"'s behaviors; and returning assigned unique identifiers for each of the at least two web service behaviors in response to the client request, to allow the client to access each behavior separately using each behavior'"'"'s assigned data communication port, wherein, based on the client request and based on the observable directory of what web service operations have occurred and in what order the operations occurred, multiple web services are run simultaneously in parallel. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. In a computing environment, a method comprising:
-
determining that a web service provided by a web services provider provides a plurality of different behaviors, the web service being identified by a unique web service identifier, wherein each web service behavior is provided by a different logical entity and wherein each web service defines which requests it is configured to receive and in which order it is configured to receive the requests; assigning a separate data communication port to each of the plurality of different web service behaviors, the assigned data communication port being different than the web service identifier, wherein the data communication port allows a client to individually address and access the logical entities that provide each of the different web service behaviors separately, without addressing the web service identifier, and wherein the data communication ports maintain a list of ports including interaction between the ports, which provides an observable directory of what web service operations have occurred and in what order the operations occurred; receiving, at a service, a request for a contract from a client, wherein the request requests web service functionality which utilizes at least two of the web service'"'"'s behaviors; providing an identifier of a contract document and an identifier of a binding list document in response to the request, the document containing contract information including a message ordering and a set of interaction points corresponding to behaviors of the service, and the binding list document containing service relationship information, such that the client can communicate directly with the logical entity within the web services provider that controls the requested behavior, wherein, based on the client request and based on the observable directory of what web service operations have occurred and in what order the operations occurred, multiple web services are run simultaneously in parallel. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30)
-
Specification