Lines Matching refs:new
11 usage of QUIC client functionality for both existing and new applications.
54 Recommended usage approaches for new applications.
106 The recommended usage mode for new applications adopting QUIC is multi-stream
158 An application may also choose to implement a custom BIO. The new
221 incoming network datagrams, use the new function L<SSL_net_read_desired(3)>;
223 informed when it is possible to transmit network datagrams, use the new function
399 must be explicitly configured by the application using the new
408 L<SSL_write(3)>), or the new function L<SSL_handle_events(3)>, regularly. If the
442 wishes to prioritise RFC conformance or rapid shutdown, consider using the new
449 The recommended usage in new applications varies depending on three independent
487 Regardless of the design decisions chosen above, it is recommended that new
494 This section details new APIs which are directly or indirectly related to QUIC.
497 The following SSL APIs are new but relevant to both QUIC and DTLS:
507 This can also be used with DTLS and supersedes L<DTLSv1_get_timeout(3)> for new
521 new usage.
615 Creates a new QUIC stream SSL object representing a new, locally-initiated QUIC
620 Potentially yields a new QUIC stream SSL object representing a new
648 This is a new BIO method which is similar to a conventional BIO pair but
653 This is a new BIO API which allows a BIO to expose a poll descriptor. This API
659 This is a new BIO API which can be implemented by BIOs which implement datagram
812 QUIC implementation can read new datagrams via a call to L<BIO_recvmmsg(3)> on
