| Article found | Fact |
|---|
|
Secure, Reliable, Transacted Web Services [FS03]
|
- provides an interoperable, transport independent approach to identifying message senders and receivers
- provides a finer grain approach to identifying specific elements within a service that send or should receive a message
- Today most systems using Web services encode the destination for a Web service message with a URL that is placed in the HTTP transport. The destination for the response is determined by the return transport address. This approach builds on the basic browser-server model of HTTP.
Using today's approach, the source and destination information are not part of the message itself. This can cause several problems. The information can be lost if a transport connection terminates (for example, if the response takes a long time and the connection times out) or if the message is forwarded by an intermediary such as a firewall.
- provides a mechanism to place the target, source and other important address information directly within the
Web service message. In short, WS-Addressing decouples address information from any specific transport model.
- In many scenarios messages are targeted directly to a service and the addressing information in the message can be described simply using a URL. But in practice, we often find that messages are targeted to specific elements or resources
within a service. For example, a coordination service might be coordinating many different tasks. The coordinator needs to
associate most incoming messages with a specific task instance that it manages and not the coordination service itself.
- provides a simple yet powerful mechanism called an endpoint reference for addressing entities managed by a service. While such information could be encoded in an ad-hoc manner within the URL of the service, the endpoint references provides a standard XML element that enables a structured approach to encoding this fine-grained addressing.
- enables Web service messages to be sent across a range of transports, through intermediaries, and it enables both asynchronous and extended duration communication patterns
- enables a sender to indicate where a response should go in a transport-independent manner. The response to a message may not necessarily go to the sender. In HTTP for example, without WS-Addressing it is impossible to specify that the response should be sent elsewhere.
|
