Lines Matching +full:in +full:- +full:band

4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\"    notice, this list of conditions and the following disclaimer in the
19 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\".ds RH "Out of band data
33 \s+2Out of band data\s0
35 Out of band data is a facility peculiar to the stream socket
38 ``urgent data'' as in-line, while the NBS protocols [Burruss81]
40 transmission channel along which out of band data is to be
43 of band message varies from protocol to protocol; everything
46 A stream socket's notion of out of band data has been defined
49 clearly this is subject to debate.  Out of band data is expected
52 band data and one outstanding out of band message are expected to
54 It is a protocol's prerogative to support larger-sized messages, or
55 more than one outstanding out of band message at a time.
57 Out of band data is maintained by the protocol and is usually not
58 stored in the socket's receive queue.
59 A socket-level option, SO_OOBINLINE,
60 is provided to force out-of-band data to be placed in the normal
63 when multiple out-of-band
66 requests to the \fIpr_usrreq\fP routine are used in sending and