Remote Procedure Call: Difference between revisions

m
Minor grammar fixes, added pre tags for drawing to be safe.
[unchecked revision][unchecked revision]
m (ported RPC page)
 
m (Minor grammar fixes, added pre tags for drawing to be safe.)
 
Line 7:
== Remote Procedure Calls in a nutshell ==
 
AAn RPC system relies on a compiler that will generate helper code from a high-level interface description (usually IDL, "or ''Interface Description Language"''). The 'client' code that wishwishes to call a service will actually call a proxy function locally, passing it the arguments for the remote code. The proxy then marshalls (or serializes) the arguments according so that they fit in a flat buffer and send that buffer to the server code (for instance involving a UDP packet or some local message queue) and waits for response.
 
OnThe itsserver side, the serverwill suddenly receive the marshalled packet and will pass it to a stub that will re-createrecreate the data (unmarshall) and call the real service procedure, getting backretrieving the results and marshall them back in a message to the client.
 
<pre>
( client ) ( server )
| ^
Line 29 ⟶ 30:
| interface) |
+--------------+
</pre>
 
[[Category:IPC]]
252

edits