Lines Matching full:applications

68 You can use OpenSSL's QUIC capabilities for both client and server applications.
69 This man page describes how to let applications use the QUIC protocol using the
74 are needed to existing applications which use libssl API to bring QUIC protocol
85 implementation requirements, which existing applications should bear in mind;
87 Aspects which must be considered by existing applications when adopting QUIC,
90 Recommended usage approaches for new applications.
103 Default stream mode is primarily for compatibility with existing applications.
104 For new applications utilizing QUIC, it's recommended to disable this mode and
105 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
132 Default stream mode is intended to aid compatibility with legacy applications.
133 New applications adopting QUIC should use multi-stream mode, described below,
139 in order to use \fBSSL_accept_stream\fR\|(3) in this case. However, applications
148 The recommended usage mode for new applications adopting QUIC is multi-stream
172 semantics. There are broadly four options for applications to use as a network
176 \&\fBBIO_s_datagram\fR\|(3), recommended for most applications, replaces
180 semantics, and is recommended for existing applications which use a BIO pair or
200 is no longer the case; applications must explicitly configure the desired
212 \&\fBBIO_s_datagram\fR\|(3) when used with QUIC, therefore applications which use this
215 \&\fBBIO_new_buffer_ssl_connect\fR\|(3) cannot be used with QUIC and applications must
219 must be shut down. In particular, applications should be advised that the full
223 is available for such applications. For details, see \fBSSL_shutdown\fR\|(3).
239 \&\fBSSL_net_write_desired\fR\|(3). Only applications which wish to manage their own event
296 .SH "CONSIDERATIONS FOR EXISTING APPLICATIONS"
297 .IX Header "CONSIDERATIONS FOR EXISTING APPLICATIONS"
298 Existing applications seeking to adopt QUIC should apply the following list to
375 Most applications will service the SSL object by calling \fBSSL_read\fR\|(3) or
388 Client applications which use thread assisted mode do not need to be concerned
402 .SH "RECOMMENDED USAGE IN NEW APPLICATIONS"
403 .IX Header "RECOMMENDED USAGE IN NEW APPLICATIONS"
404 The recommended usage in new applications varies depending on three independent
426 Applications which wish to implement QUIC-specific protocols should be aware of
433 applications avoid use of the default stream mode and use the multi-stream API
675 OpenSSL's QUIC implementation is designed to facilitate applications which wish
677 applications which wish to use the SSL APIs in a nonblocking fashion and manage