Lines Matching +full:application +full:- +full:dependent
10 inet6_rth_segments, inet6_rth_getaddr \- Routing header manipulation
14 \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lsocket\fR [\fIlibrary\fR]
89 To receive a routing header, the application must enable the
105 To send a routing header, the application specifies it either as ancillary data
108 described in \fIRFC-2460\fR. Applications can specify no more than one outgoing
112 The application can remove any sticky routing header by calling
116 When using ancillary data, a routing header is passed between the application
120 implementation-dependent and should not be accessed directly by the
121 application, but should be accessed using the \fBinet6_rth\fR functions.
138 currently defines only the Type 0 header. See \fIRFC-2460\fR. The Type 0 header
151 function returns \fB0\fR upon success and \fB-1\fR upon failure.
154 The \fBinet6_rth_reverse()\fR function returns \fB0\fR upon success or \fB-1\fR
159 and \fB-1\fR upon an error.
182 MT-Level Safe
188 RFC 3542- \fIAdvanced Sockets Application Programming Interface (API) for