Message Passing Systems
Distributed object and remote method invocation systems like ONC RPC, CORBA, Java RMI, DCOM, SOAP, .NET Remoting, CTOS, QNX Neutrino RTOS, OpenBinder, D-Bus, Unison RTOS and similar are message passing systems.
Message passing systems have been called "shared nothing" systems because the message passing abstraction hides underlying state changes that may be used in the implementation of sending messages.
Message passing model based programming languages typically define messaging as the (usually asynchronous) sending (usually by copy) of a data item to a communication endpoint (Actor, process, thread, socket, etc.). Such messaging is used in Web Services by SOAP. This concept is the higher-level version of a datagram except that messages can be larger than a packet and can optionally be made reliable, durable, secure, and/or transacted.
Messages are also commonly used in the same sense as a means of interprocess communication; the other common technique being streams or pipes, in which data are sent as a sequence of elementary data items instead (the higher-level version of a virtual circuit).
Read more about this topic: Message Passing
Famous quotes containing the words message, passing and/or systems:
“Children in home-school conflict situations often receive a double message from their parents: The school is the hope for your future, listen, be good and learn and the school is your enemy. . . . Children who receive the school is the enemy message often go after the enemyact up, undermine the teacher, undermine the school program, or otherwise exercise their veto power.”
—James P. Comer (20th century)
“Toll on, thou passing bell;
Ring out my doleful knell;”
—George Boleyn (d. 1536)
“The only people who treasure systems are those whom the whole truth evades, who want to catch it by the tail. A system is just like truths tail, but the truth is like a lizard. It will leave the tail in your hand and escape; it knows that it will soon grow another tail.”
—Ivan Sergeevich Turgenev (18181883)