Message Passing Versus Calling
Message passing should be contrasted with the alternative communication method for passing information between programs – the Call. In a traditional Call, arguments are passed to the "callee" (the receiver) typically by one or more general purpose registers or in a parameter list containing the addresses of each of the arguments. This form of communication differs from message passing in at least three crucial areas:
- total memory usage
- transfer time
- locality
In message passing, each of the arguments has to have sufficient available extra memory for copying the existing argument into a portion of the new message. This applies irrespective of the size of the original arguments – so if one of the arguments is (say) an HTML string of 31,000 octets describing a web page (similar to the size of this article), it has to be copied in its entirety (and perhaps even transmitted) to the receiving program (if not a local program).
By contrast, for the call method, only an address of say 4 or 8 bytes needs to be passed for each argument and may even be passed in a general purpose register requiring zero additional storage and zero "transfer time". This of course is not possible for distributed systems since an (absolute) address – in the callers address space – is normally meaningless to the remote program (however, a relative address might in fact be usable if the callee had an exact copy of, at least some of, the callers memory in advance). Web browsers and web servers are examples of processes that communicate by message passing. A URL is an example of a way of referencing resources that does depend on exposing the internals of a process.
A subroutine call or method invocation will not exit until the invoked computation has terminated. Asynchronous message passing, by contrast, can result in a response arriving a significant time after the request message was sent.
A message handler will, in general, process messages from more than one sender. This means its state can change for reasons unrelated to the behaviour of a single sender or client process. This is in contrast to the typical behaviour of an object upon which methods are being invoked: the latter is expected to remain in the same state between method invocations. (in other words, the message handler behaves analogously to a volatile object).
Read more about this topic: Message Passing
Famous quotes containing the words message, passing and/or calling:
“Christina Bailey: I was just thinking how much you can tell about a person from such simple things. Your car, for instance.
Mike Hammer: Now what kind of message does it send you?
Christina: You have only one real, lasting love.
Mike: Now who could that be?
Christina: You. You’re one of those self-indulgent males who thinks about nothing but his clothes, his car, himself. I’ll bet you do push-ups every morning just to keep your belly hard.”
—A.I. (Albert Isaac)
“I not deny
The jury, passing on the prisoner’s life,
May in the sworn twelve have a thief or two
Guiltier than him they try. What’s open made to justice,
That justice seizes.”
—William Shakespeare (1564–1616)
“These are the voices of the pastors calling
And calling like the long echoes in long sleep,
Generations of shepherds to generations of sheep.”
—Wallace Stevens (1879–1955)