.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "XDR_INIT_ENCODE" "9" "09 October 2005" "" ""

.SH NAME
xdr_init_encode \- Initialize a struct xdr_stream for sending data.
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void xdr_init_encode  (struct xdr_stream * \fIxdr\fB, struct xdr_buf * \fIbuf\fB, uint32_t * \fIp\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIxdr\fB\fR
pointer to xdr_stream struct
.TP
\fB\fIbuf\fB\fR
pointer to XDR buffer in which to encode data
.TP
\fB\fIp\fB\fR
current pointer inside XDR buffer
.SH "NOTE"
.PP
at the moment the RPC client only passes the length of our
scratch buffer in the xdr_buf's header kvec. Previously this
meant we needed to call \fBxdr_adjust_iovec\fR after encoding the
data. With the new scheme, the xdr_stream manages the details
of the buffer length, and takes care of adjusting the kvec
length for us.