Lines Matching full:calls

21 remote procedure calls (explained below), and who want to understand
45 What are remote procedure calls?  Simply put, they are the high-level
52 packet arrives, the server calls a dispatch routine, performs whatever
90 implementation mechanisms.  They simply make remote procedure calls
96 RPC calls are made with the system routines
126 remote procedure calls can be made from any language.
270 The simplest interface, which explicitly makes RPC calls, uses the
317 The simplest way of making remote procedure calls is with the RPC
398 Normally, a server registers all of the RPC calls it plans
444 thus, it is always safe in conjunction with calls generated by
453 main procedure calls
456 function that calls the remote procedures in response to RPC
616 has only two parameters, and is thus OK.  It calls
747 Here is a final example that calls the previously written
789 and the system calls for dealing with them.
793 which restricts RPC calls to 8K bytes of data.  Using TCP permits calls
889 on which to receive and reply to RPC calls.  Otherwise,
1221 uses UDP, thus it calls
1267 All RPC calls using that
1367 broadcast RPC and normal RPC calls:
1454 RPC messages can be placed in a \*Qpipeline\*U of calls
1459 2) the pipeline of calls is transported on a reliable
1462 the client can generate new calls in parallel
1463 with the server executing previous calls.
1470 and the total elapsed time of a series of calls.
1472 Since the batched calls are buffered,
1478 has two similar calls: one renders a string and returns void results,
1573 the client must perform RPC calls on a TCP-based transport
1574 and the actual calls must have the following attributes:
1732 by invoking the appropriate system calls.
1923 .I "Remote Procedure Calls: Protocol Specification"
1976 The last argument to both of these calls,