4 ms·
> There's an exception to this rule if the underlying network does not go wrong. Fair enough. Maybe we shouldn't call it remote procedure calls then, because i
by valenterry 3y ago
> There's an exception to this rule if the underlying network does not go wrong.
Fair enough. Maybe we shouldn't call it remote procedure calls then, because it's not remote anymore. The word remote exists to make the distinction compared to local. If there is no distinction in a given context, there is no need to use that word from the beginning.
- JonChesterfield 3y agoMaybe? Say one processor is an aarch64 core and another is x64, but someone has put them on the same memory subsystem and the system as a whole tends to die if either falls over. And then you want to make a function call from one to the other - it isn't as remote as another machine, but you can't pass things in registers either. "Remote" call seems a reasonable description to use for that but as the semantics are indeed different perhaps a new term should be used.