Lines Matching full:routine

52 packet arrives, the server calls a dispatch routine, performs whatever
81 a C routine which returns the number of users on a remote machine.
175 You can do this by calling the RPC library routine
230 Routine&Description
318 library routine
424 routine registers a C procedure as corresponding to a
608 Note that the routine
619 As an example of a user-defined type routine,
656 An XDR routine returns nonzero (true in the sense of C) if it
700 This routine takes as parameters the XDR handle,
704 and an XDR routine for handling each array element.
730 That is the reason for the XDR routine
740 routine, which is the same as
897 (the low-level client routine) must match.
951 The user routine
972 The user service routine serializes the results and returns
977 handle, the second is the XDR routine,
1020 The relevant routine is
1024 handle, the XDR routine,
1042 As an example, consider the following XDR routine
1072 you would have to rewrite this routine in the following way:
1105 is NULL.  For example, in the routine
1112 To summarize, each XDR routine is responsible
1114 When an XDR routine is called from
1211 the XDR routine for serializing the argument,
1213 the XDR routine for deserializing the return value,
1353 RPC library routine is called, because descriptors are constantly
1405 	xdrproc_t inproc;         /* \fIxdr routine for args\fP */
1407 	xdrproc_t outproc;        /* \fIxdr routine for results\fP */
1433 Otherwise, the routine waits for another response.
1437 the routine returns with
1575 1) the result's XDR routine must be zero
1744 since the RPC package passes the service dispatch routine a request
1746 Consider the fields of a request handle passed to a service dispatch routine:
1781 to the service dispatch routine:
2082 Note the use of the routine
2097 creation routine should be called in the following form:
2263  * The xdr routine:
2456 The routine
2462 routine itself.  The call to
2551 routine.
2648 int pnum;		/* \fIprogram number for callback routine\fP */