This manual provides an overview of high-level programming with open network computing remote procedure calls (ONC RPC), describes how to use the rpcgen protocol compiler to create applications, and describes the RPC programming interface. See rpcgen(1) for more information.
This guide assumes a knowledge of network theory and is for experienced programmers who want to write network applications using open-network computing remote procedure calls (ONC RPC) without needing to know about the underlying network.
This guide contains three chapters, an appendix, and an index:
Chapter 1 |
Provides an overview of high-level programming through remote procedure
calls (RPC), and discusses the RPC model and versions, external data
representation, and RPC independence from network transport protocol.
This chapter is for anyone interested in ONC RPC. |
Chapter 2 |
Describes how to write RPC client and server applications with the
rpcgen
protocol compiler. It also provides some information on
rpcgen,
client and server programming, debugging applications, the C preprocessor,
and RPC language syntax.
This chapter also describes how
to create routines for external data representation (XDR).
This chapter is for programmers who want to use rpcgen to write RPC-based network applications. |
Chapter 3 |
Describes the RPC programming interface layers, XDR serialization defaults,
raw RPC, and miscellaneous RPC features.
This chapter is for programmers who need to understand RPC mechanisms to write customized network applications. |
Appendix A | Contains additional notes on the XDR library. This appendix is for programmers who want to implement RPC and XDR on new machines. |
The contents of this manual have not changed since the previous release.
Audience | Icon | Color Code |
General users | G | Blue |
System and network administrators | S | Red |
Programmers | P | Purple |
Device driver writers | D | Orange |
Reference page users | R | Green |
Some books in the documentation set help meet the needs of several audiences. For example, the information in some system books is also used by programmers. Keep this in mind when searching for information on specific topics.
The Documentation Overview, Glossary, and Master Index provides information on all of the books in the Digital UNIX documentation set.
Digital welcomes any comments and suggestions you have on this and other Digital UNIX manuals.
You can send your comments in the following ways:
A Reader's Comment form is located on your system in the following location:
/usr/doc/readers_comment.txt
Digital Equipment Corporation
UEG Publications Manager
ZK03-3/Y32
110 Spit Brook Road
Nashua, NH 03062-9987
A Reader's Comment form is located in the back of each printed manual. The form is postage paid if you mail it in the United States.
Please include the following information along with your comments:
The Digital UNIX Publications group cannot respond to system problems or technical support inquiries. Please address technical questions to your local system vendor or to the appropriate Digital technical support office. Information provided with the software media explains how to send problem reports to Digital.
This document uses the following conventions:
%
$ |
A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne and Korn shells. |
% cat | Boldface type in interactive examples indicates typed user input. |
file | Italic (slanted) type indicates variable values, placeholders, and function argument names. |
[ | ]
{ | } |
In syntax definitions, brackets indicate items that are optional and braces indicate items that are required. Vertical bars separating items inside brackets or braces indicate that you choose one item from among those listed. |
. . . | In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times. |
cat(1) | A cross-reference to a reference page includes the appropriate section number in parentheses. For example, cat(1) indicates that you can find information on the cat command in Section 1 of the reference pages. |