Lines Matching full:semantics
127 for TLS connections and do not have changed semantics, with some exceptions. The
128 changes to the semantics of existing APIs are as follows:
136 semantics. There are broadly four options for applications to use as a network
149 semantics, and is recommended for existing applications which use a BIO pair or
155 datagram semantics. Unlike L<BIO_s_dgram_pair(3)>, it is unidirectional.
183 application can still enjoy blocking semantics for calls to application-level
370 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
380 L<BIO_s_dgram_pair(3)> instead, which has the necessary datagram semantics. You
382 and to use datagram semantics when interacting with the L<BIO_s_dgram_pair(3)>
391 semantics. L<BIO_sendmmsg(3)> and L<BIO_recvmmsg(3)> must be implemented. These
394 desired. Implementing these methods is required if blocking semantics at the SSL
604 Configures whether blocking semantics are used at the application level. This
723 provides datagram semantics.
734 semantics. It is implemented by L<BIO_s_datagram(3)> and L<BIO_s_dgram_pair(3)>.
739 By default, L<BIO_s_dgram_pair(3)> has semantics comparable to those of Berkeley
740 sockets being used with datagram semantics. This allows an alternative mode
756 Local addressing support refers to the ability of a BIO with datagram semantics
814 It should provide read and write BIOs with nonblocking datagram semantics to