Lines Matching +full:out +full:- +full:of +full:- +full:band

2 .\"	The Regents of the University of California.  All rights reserved.
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\"    notice, this list of conditions and the following disclaimer.
10 .\"    notice, this list of conditions and the following disclaimer in the
12 .\" 3. Neither the name of the University nor the names of its contributors
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
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
37 to what its semantics should be.  TCP defines the notion of
38 ``urgent data'' as in-line, while the NBS protocols [Burruss81]
40 transmission channel along which out of band data is to be
42 In addition, the amount of the data which may be sent as an out
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
50 to be transmitted out of the normal sequencing and flow control
51 constraints of the data stream.  A minimum of 1 byte of out of
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
59 A socket-level option, SO_OOBINLINE,
60 is provided to force out-of-band data to be placed in the normal
62 this sometimes amelioriates problems due to loss of data
63 when multiple out-of-band