Lines Matching full:procedure

11 .OH 'Remote Procedure Call Programming Guide''Page %'
12 .EH 'Page %''Remote Procedure Call Programming Guide'
14 \&Remote Procedure Call Programming Guide
21 remote procedure calls (explained below), and who want to understand
45 What are remote procedure calls?  Simply put, they are the high-level
51 makes a procedure call to send a data packet to the server.  When the
53 service is requested, sends back the reply, and the procedure call returns
62 For a complete specification of the routines in the remote procedure
83 call a procedure, just as they would call
90 implementation mechanisms.  They simply make remote procedure calls
103 obtains a unique system-wide procedure-identification number, and
105 actually executes a remote procedure call.  At the middle level, a
126 remote procedure calls can be made from any language.
305 Each RPC procedure is uniquely defined by a program number,
306 version number, and procedure number.  The program number
308 which has a different procedure number.  Each program also
310 remote service (adding a new procedure, for example), a new
312 to call a procedure to find the number of remote users, you
313 look up the appropriate program, version and procedure numbers
317 The simplest way of making remote procedure calls is with the RPC
321 machine.  The next three parameters are the program, version, and procedure
322 numbers\(emtogether they identify the procedure to be called.
324 be encoded and passed to the remote procedure.
326 returned by the remote procedure and a pointer to the place where
327 the procedure's results are to be stored.  Multiple arguments and
368 The remote server procedure
391 of the remote procedure call (ignored in our example),
400 In this example, there is only a single procedure
424 routine registers a C procedure as corresponding to a
425 given RPC procedure number.  The first three parameters,
430 are the program, version, and procedure numbers
431 of the remote procedure to be registered;
433 is the name of the local procedure that implements the remote
434 procedure; and
438 are the XDR filters for the remote procedure's arguments and
452 After registering the local procedure, the server program's
453 main procedure calls
455 the RPC library's remote procedure dispatcher.  It is this
458 remote procedure arguments and encoding results, using the XDR
459 filters specified when the remote procedure was registered.
596 can be a built-in procedure like
937 with the procedure
949 rather than procedure, level.
954 based on the procedure number.
961 The first is that procedure
966 Second, there is a check for invalid procedure numbers.
981 As an example, we can add a procedure
1210 pointer, the procedure number,
1404 	u_long    procnum;        /* \fIprocedure number\fP */
1412 The procedure
1568 Of course the service could have one procedure
1570 to indicate whether or not the procedure should respond.
1757     u_long    rq_proc;    	/* \fIdesired procedure number\fP */
1923 .I "Remote Procedure Calls: Protocol Specification"
2195 Both versions can be handled by the same C procedure:
2256 This also illustrates an XDR procedure that behaves differently