Lines Matching full:protocols
48 program in order to be forward compatible with changing protocols.
94 The RPC protocol is independent of transport protocols. That is, RPC
139 connection-oriented protocols. For example, a request-reply protocol
165 Several different authentication protocols can be supported. A field
167 information on specific authentication protocols can be found in the
168 \fIAuthentication Protocols\fP\,
205 version number of 1. Because most new protocols evolve into better,
206 stable, and mature protocols, a version field of the call message
208 Version numbers make speaking old and new protocols through the same
217 Just as remote program protocols may change over several versions,
276 \fIAuthentication Protocols\fP\,
277 below, for definitions of the various authentication protocols.)
318 other (non-RPC) protocols can be implemented. Sun currently uses, or
320 (non-RPC) protocols: batching (or pipelining) and broadcast RPC.
321 These two protocols are discussed but not defined below.
327 stream protocols (like TCP/IP) for its transport. In the case of
335 In broadcast RPC-based protocols, the client sends a broadcast packet
337 unreliable, packet-based protocols (like UDP/IP) as its transports.
338 Servers that support broadcast protocols only respond when the
538 \&Authentication Protocols
1218 The portmapper program currently supports two protocols (UDP/IP and
1220 port number 111 (SUNRPC [8]) on either of these protocols. The