Lines Matching refs:to
28 pair is similar to a BIO pair (see L<BIO_s_bio(3)>) but has datagram semantics.
29 Broadly, this means that the length of the buffer passed to a write call will
30 match that retrieved by a read call. If the buffer passed to a read call is too
34 The BIO datagram pair attaches certain metadata to each write, such as source
37 A typical application of a BIO datagram pair is to allow an application to keep
40 The BIO datagram pair is designed to support multithreaded use where certain
43 The BIO datagram pair allows each half of a pair to signal to the other half
46 BIO_new_bio_dgram_pair() combines the calls to L<BIO_new(3)>,
47 L<BIO_make_bio_pair(3)> and L<BIO_set_write_buf_size(3)> to create a connected
51 L<BIO_make_bio_pair(3)> may be used to join two datagram pair BIOs into a pair.
59 that the opposite BIO in the pair will no longer have any data waiting to be
63 further writes will fail until the buffer is drained via calls to
68 which is attached to each datagram, such as source and destination addresses.
72 size of the next datagram waiting to be read in bytes. An application can use
73 this function to ensure it provides an adequate buffer to a subsequent read
74 call. If no datagram is waiting to be read, zero is returned.
77 zero-length buffer to BIO_write is treated as a no-op.
80 connected to a peer BIO.
83 large a datagram the next call to L<BIO_write(3)> can accept. If there is not
84 enough space in the write buffer to accept another datagram equal in size to the
85 configured MTU, zero is returned (see below). This is intended to avoid a
86 situation where an application attempts to read a datagram from a network
87 intending to write it to a BIO datagram pair, but where the received datagram
88 ends up being too large to write to the BIO datagram pair.
92 is enabled, BIO_read() will fail if the buffer provided is inadequate to hold
93 the next datagram to be read. If no-truncate mode is disabled (the default), the
97 BIO_dgram_set_mtu() and BIO_dgram_get_mtu() may be used to set an informational
102 code to determine a requested MTU. When a BIO datagram pair BIO is created, the
103 MTU is set to an unspecified but valid value.
120 other BIO call is also in progress to either half of the same BIO datagram pair
125 The BIO datagram pair can be used to enqueue datagrams which have source and
128 honour any source and destination addresses it attaches to each datagram. For
130 by simple calls to L<BIO_read(3)>, the destination addresses will be discarded.
135 be set via a call to BIO_dgram_set_caps(), and these capabilities will be
139 controls the capabilities advertised to the peer, and
149 The user of the datagram pair BIO promises to honour source addresses provided
150 with datagrams written to the BIO pair.
154 The user of the datagram pair BIO promises to honour destination addresses provided
155 with datagrams written to the BIO pair.
160 addressing information with future writes to the BIO pair, where available.
165 destination addressing information with future writes to the BIO pair, where
170 If a caller attempts to specify a destination address (for example, using
175 If a caller attempts to specify a source address when writing, or requests a
179 If a caller attempts to enable local address support using
186 indicate that the application using that half of a BIO datagram pair promises to
187 provide source and destination addresses respectively when writing datagrams to
