Lines Matching full:which

74 are needed to existing applications which use libssl API to bring QUIC protocol
84 The changes to existing libssl APIs which are driven by QUIC-related
85 implementation requirements, which existing applications should bear in mind;
87 Aspects which must be considered by existing applications when adopting QUIC,
88 including potential changes which may be needed.
96 stream mode, which is intended to provide compatibility with existing non-QUIC
117 When default stream mode is used, any API function which can be called on a QUIC
118 stream SSL object can also be called on a QUIC connection SSL object, in which
149 mode, in which no default stream is attached to the QUIC connection SSL object
161 with the connection, calls to API functions which are defined as operating on a
180 semantics, and is recommended for existing applications which use a BIO pair or
212 \&\fBBIO_s_datagram\fR\|(3) when used with QUIC, therefore applications which use this
221 may not be suitable for short-lived processes which should exit immediately
239 \&\fBSSL_net_write_desired\fR\|(3). Only applications which wish to manage their own event
273 TLS Next Protocol Negotiation cannot be used and is superseded by ALPN, which
281 Some cipher suites which are generally available for TLSv1.3 are not available
309 Determine how to provide QUIC with network access. Determine which of the below
313 Your application uses \fBBIO_s_socket\fR\|(3) to construct a BIO which is passed to
322 construct a BIO which is passed to the SSL object to provide it with network
340 \&\fBBIO_s_dgram_pair\fR\|(3) instead, which has the necessary datagram semantics. You
382 If the SSL object is being used with an underlying network BIO which is pollable
385 resources which can be used to determine when \fBSSL_handle_events\fR\|(3) should be
388 Client applications which use thread assisted mode do not need to be concerned
418 which enables QUIC to achieve higher performance and more accurate connection
426 Applications which wish to implement QUIC-specific protocols should be aware of
427 the APIs listed under \fBQUIC-SPECIFIC APIS\fR which provide access to
438 This section details new APIs which are directly or indirectly related to QUIC.
452 This is a non-specific I/O operation which makes a best effort attempt to
466 Creates a listener SSL object, which differs from an ordinary SSL object in that
475 Creates a listener SSL object which is subordinate to a QUIC domain SSL object
483 Returns an SSL object pointer (potentially to the same object on which it is
504 which does accept incoming connections (i.e., which was not created using
505 \&\fBSSL_LISTENER_FLAG_NO_ACCEPT\fR), leading to a UDP network endpoint which has
528 When an SSL object is being used with an underlying network read BIO which
529 supports polling, \fBSSL_get_rpoll_descriptor\fR\|(3) outputs an OS resource which
530 can be used to synchronise on network readability events which should result in
569 This allows an application to determine the application error code which was
570 signalled by a peer which has performed a non-normal stream termination of the
574 This allows an application to determine the error code which was signalled when
584 Provides information on the kind of QUIC stream which is attached
588 Returns the QUIC stream ID which the QUIC protocol has associated with a QUIC
616 This is a new BIO method which is similar to a conventional BIO pair but
620 This is a new BIO API which allows a BIO to expose a poll descriptor. This API
625 This is a new BIO API which can be implemented by BIOs which implement datagram
632 to be enabled in which datagrams will not be silently truncated if they are
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
684 a structure which expresses some kind of OS resource which can be used to
690 Broadly, an application which wishes to manage its own event loop should
707 a \fBBIO_s_datagram\fR\|(3), or a custom BIO which implements
713 \&\fBSSL_get_wpoll_descriptor\fR\|(3) to identify OS resources which can be used for
718 writability events on the underlying network BIO which was provided, and call