Re: "compilation" and "semantics" difference between RPC and ordinary procedure call
- From: torbenm@xxxxxxxxxxxxx (Torben Ægidius Mogensen)
- Date: Mon, 19 Mar 2007 10:28:54 +0100
"new_dude" <yjaplomb@xxxxxxxxx> writes:
Can someone here tell me the difference between RPC and ordinary
procedure call in terms of "compilation" and "semantics"?
Semantically, a remote procedure call should ideally behave exactly as
a normal procedure call, so changing a call from normal to remote or
vice versa has no sematic effect. However, because a RPC is often
executed in parallel with the caller, side effects may come in a
different sequence. Also, aince RPCs require marshalling of arguments
and results, this may put some limitations to what argument and result
types are possible.
In terms of compilation, there are huge differences. I mentioned
marshalling, but there are also synchronisation issues.
Note: This is NOT a homework assignment. It is a question from
practice midterm, so I am not doing anything wrong.
Except you aren't practicing. :-)
Torben
.
- References:
- Prev by Date: Efficient algorithm?
- Next by Date: Re: Efficient algorithm?
- Previous by thread: "compilation" and "semantics" difference between RPC and ordinary procedure call
- Next by thread: Re: "compilation" and "semantics" difference between RPC and ordinary procedure call
- Index(es):