WebSeitz/wikilog
Message Exchange Pattern
Whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government, laying its foundation on such principles and organizing its powers in such form, as to them shall seem most likely to effect their Safety and Happiness.

(backlinks off) (map off)
(search off)
last edited by BillSeitz on Aug 22, 2008 8:37 pm

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

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

discussed in the concept of quite often

says that the only fundamental performance limitations in are: 1) Headers, 2) Request-Response Message Exchange Pattern. 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. 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 company

http://activemq.codehaus.org/REST

See : |


 



Bill Seitz, fluxent at gmail dot com, Weblog