unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (SunOS-4.1.3)
Page:
Section:
Apropos / Subsearch:
optional field

RPC_XDR(3N)                                                        RPC_XDR(3N)



NAME
       xdr_accepted_reply,   xdr_authunix_parms,   xdr_callhdr,   xdr_callmsg,
       xdr_opaque_auth, xdr_rejected_reply, xdr_replymsg -  XDR  library  rou-
       tines for remote procedure calls

DESCRIPTION
       These  routines  are  used  for describing the RPC messages in XDR lan-
       guage.  They should normally be used by those who do not  want  to  use
       the RPC package.

   Routines
       The XDR data structure is defined in the RPC/XDR Library Definitions of
       the

       #include <&lt;rpc/rpc.h>&gt;

       bool_t xdr_accepted_reply(xdrs, arp)
       XDR *xdrs;
       struct accepted_reply *arp;

              Used for encoding RPC reply messages.  It encodes the status  of
              the  RPC call in the XDR language format and in the case of suc-
              cess, it encodes the call results as well.  This routine is use-
              ful  for  users  who wish to generate RPC-style messages without
              using the RPC package. This routine returns TRUE if it succeeds,
              FALSE otherwise.

       bool_t xdr_authunix_parms(xdrs, aup)
       XDR *xdrs;
       struct authunix_parms *aup;

              Used for describing UNIX credentials.  It encludes machine name,
              user ID, group ID list, etc.  This routine is useful  for  users
              who  wish  to  generate  these credentials without using the RPC
              authentication package.  This routine returns TRUE  if  it  suc-
              ceeds, FALSE otherwise.

       void xdr_callhdr(xdrs, chdrp)
       XDR *xdrs;
       struct rpc_msg *chdrp;

              Used  for  describing  RPC call header messages.  It encodes the
              static part of the call message header in the XDR language  for-
              mat.   It  includes information such as transaction ID, RPC ver-
              sion number, program number, and version number.   This  routine
              is  useful  for  users  who  wish to generate RPC-style messages
              without using the RPC package.

       bool_t xdr_callmsg(xdrs, cmsgp)
       XDR *xdrs;
       struct rpc_msg *cmsgp;

              Used for describing RPC call messages.  It includes all the  RPC
              call  information  such  as  transaction ID, RPC version number,
              program number, version number, authentication information, etc.
              This  routine is useful for users who wish to generate RPC-style
              messages without using the RPC package.   This  routine  returns
              TRUE if it succeeds, FALSE otherwise.

       bool_t xdr_opaque_auth(xdrs, ap)
       XDR *xdrs;
       struct opaque_auth *ap;

              Used  for  describing  RPC  authentication information messages.
              This routine is useful for users who wish to generate  RPC-style
              messages  without  using  the RPC package.  This routine returns
              TRUE if it succeeds, FALSE otherwise.

       bool_t xdr_rejected_reply(xdrs, rrp)
       XDR *xdrs;
       struct rejected_reply *rrp;

              Used for describing RPC reply messages.  It encodes the rejected
              RPC message in the XDR language format.  The message is rejected
              either because of version number mismatch or because of  authen-
              tication  errors.   This routine is useful for users who wish to
              generate RPC-style messages without using the RPC package.  This
              routine returns TRUE if it succeeds, FALSE otherwise.

       bool_t xdr_replymsg(xdrs, rmsgp)
       XDR *xdrs;
       struct rpc_msg *rmsgp;

              Used  for  describing  RPC  reply  messages.  It encodes the RPC
              reply message in the XDR language format.  This reply  could  be
              an  acceptance,  rejection, or NULL.  This routine is useful for
              users who wish to generate RPC style messages without using  the
              RPC  package.   This  routine returns TRUE if it succeeds, FALSE
              otherwise.

SEE ALSO
       rpc(3N)



                                20 January 1990                    RPC_XDR(3N)