Lines Matching full:semantics
167 for TLS connections and do not have changed semantics, with some exceptions. The
168 changes to the semantics of existing APIs are as follows:
172 semantics. There are broadly four options for applications to use as a network
180 semantics, and is recommended for existing applications which use a BIO pair or
184 datagram semantics. Unlike \fBBIO_s_dgram_pair\fR\|(3), it is unidirectional.
205 application can still enjoy blocking semantics for calls to application-level
332 of such a buffer is incompatible with QUIC as QUIC requires datagram semantics
340 \&\fBBIO_s_dgram_pair\fR\|(3) instead, which has the necessary datagram semantics. You
342 and to use datagram semantics when interacting with the \fBBIO_s_dgram_pair\fR\|(3)
349 semantics. \fBBIO_sendmmsg\fR\|(3) and \fBBIO_recvmmsg\fR\|(3) must be implemented. These
352 desired. Implementing these methods is required if blocking semantics at the SSL
521 Configures whether blocking semantics are used at the application level. This
617 provides datagram semantics.
626 semantics. It is implemented by \fBBIO_s_datagram\fR\|(3) and \fBBIO_s_dgram_pair\fR\|(3).
630 By default, \fBBIO_s_dgram_pair\fR\|(3) has semantics comparable to those of Berkeley
631 sockets being used with datagram semantics. This allows an alternative mode
644 Local addressing support refers to the ability of a BIO with datagram semantics
693 It should provide read and write BIOs with nonblocking datagram semantics to