Message Exchange Pattern

a type of design pattern that describe distributed communications. http://www.serviceoriented.org/message_exchange_pattern.html

HTTP has both a fixed connection model and message exchange pattern; the client identifies the server through a URI, connects to it, issues a HTTP request message, and receives a HTTP response message. http://lists.w3.org/Archives/Public/xml-dist-app/2001Jul/att-0232/binding.html

discussed in the concept of SOAP quite often

Mark Nottingham says that the only fundamental performance limitations in HTTP are: 1) Headers, 2) Request-Response Message Exchange Pattern. HTTP is fundamentally request/response; however, one-way messages in either direction are easily accommodated with only the overhead of a small one-packet message in the other direction. KnowNow and others have also found interesting ways around this limitation.

Something like http://www.mnot.net/blog/2003/09/13/click_submit_only_once combined with any JMS implementation http://seanmcgrath.blogspot.com/2004_07_18_seanmcgrath_archive.html#109024396294277146

also Bill De Hora company

http://activemq.codehaus.org/ReST