Asynchronous vs Request-Reply vs One Way

Definition of Asynchronous:

http://www.w3.org/TR/xmlp-scenarios/#DS17

"A sender sends a message asynchronously to a receiver expecting some response at a later time. The sender tags the request with an identifier allowing the response to be correlated with the originating request. The sender may also tag the message with an identifier for another service (other than the originating sender) which will be the recipient of the response. "


Definition of Fire and Forget (aka One Way Message, Request-Only)


http://www.w3.org/TR/xmlp-scenarios/#S1

"A sender wishes to send an unacknowledged message to a single receiver"

Under certain interpretations, the Fire and Forget is a subcase of Asynchronous - without callback.


Definition of Request-Reply

http://www.w3.org/TR/xmlp-scenarios/#S3

Unlike popular belief, Request-Reply doesn't necessarily means the reply is sent back in the same thread. One can have a Asynchronous Request-Reply scenario.