3 ms·
I worked with a system recently that did remote procedure calls. You'd invoke it locally, and it would arrange for the source code of the procedure, the argume
by dekhn 5y ago
I worked with a system recently that did remote procedure calls. You'd invoke it locally, and it would arrange for the source code of the procedure, the arguments, and the output variables to be pickled and sent to the server. does that truly differ from an x86 executable pushing arguments on a stack and jump/returning to a subroutine?
- Jtsummers 5y agoYes it does. The failure modes are different and so the switch to an RPC from a local call is not transparent. Which is what Tanenbaum discusses in the original paper and this review mostly talks past or restates hut misinterprets. https://www.win.tue.nl/~johanl/educ/2II45/2010/Lit/Tanenbaum%20RPC%2088.pdf https://www.win.tue.nl/~johanl/educ/2II45/2010/Lit/Tanenbaum...
- dekhn 5y agoMany of the things he says in that article bear no resemblance to how problems are solved in the modern era. Nobody other than andrew seems to believe strongly that "transparency" is a required component of procedure calls.