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:
“I will meditate the while upon some horrid message for a challenge.”
—William Shakespeare (1564–1616)
“He had the oaks for heating and for light.
He had a hen, he had a pig in sight.
He had a well, he had the rain to catch.
He had a ten-by-twenty garden patch.
Nor did he lack for common entertainment.
That I assume was what our passing train meant.”
—Robert Frost (1874–1963)
“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 truth’s 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 (1818–1883)