Lines Matching full:which

16 are needed to existing applications which use libssl API to bring QUIC protocol
32 The changes to existing libssl APIs which are driven by QUIC-related
33 implementation requirements, which existing applications should bear in mind;
37 Aspects which must be considered by existing applications when adopting QUIC,
38 including potential changes which may be needed.
53 stream mode, which is intended to provide compatibility with existing non-QUIC
75 When default stream mode is used, any API function which can be called on a QUIC
76 stream SSL object can also be called on a QUIC connection SSL object, in which
108 mode, in which no default stream is attached to the QUIC connection SSL object
120 with the connection, calls to API functions which are defined as operating on a
149 semantics, and is recommended for existing applications which use a BIO pair or
192 L<BIO_s_datagram(3)> when used with QUIC, therefore applications which use this
205 may not be suitable for short-lived processes which should exit immediately
225 L<SSL_net_write_desired(3)>. Only applications which wish to manage their own event
282 TLS Next Protocol Negotiation cannot be used and is superseded by ALPN, which
296 Some cipher suites which are generally available for TLSv1.3 are not available
340 Determine how to provide QUIC with network access. Determine which of the below
347 Your application uses L<BIO_s_socket(3)> to construct a BIO which is passed to
358 construct a BIO which is passed to the SSL object to provide it with network
380 L<BIO_s_dgram_pair(3)> instead, which has the necessary datagram semantics. You
427 If the SSL object is being used with an underlying network BIO which is pollable
430 resources which can be used to determine when L<SSL_handle_events(3)> should be
433 Client applications which use thread assisted mode do not need to be concerned
476 which enables QUIC to achieve higher performance and more accurate connection
488 Applications which wish to implement QUIC-specific protocols should be aware of
489 the APIs listed under B<QUIC-SPECIFIC APIS> which provide access to
501 This section details new APIs which are directly or indirectly related to QUIC.
519 This is a non-specific I/O operation which makes a best effort attempt to
538 Creates a listener SSL object, which differs from an ordinary SSL object in that
548 Creates a listener SSL object which is subordinate to a QUIC domain SSL object
558 Returns an SSL object pointer (potentially to the same object on which it is
583 which does accept incoming connections (i.e., which was not created using
584 B<SSL_LISTENER_FLAG_NO_ACCEPT>), leading to a UDP network endpoint which has
612 When an SSL object is being used with an underlying network read BIO which
613 supports polling, L<SSL_get_rpoll_descriptor(3)> outputs an OS resource which
614 can be used to synchronise on network readability events which should result in
660 This allows an application to determine the application error code which was
661 signalled by a peer which has performed a non-normal stream termination of the
666 This allows an application to determine the error code which was signalled when
679 Provides information on the kind of QUIC stream which is attached
684 Returns the QUIC stream ID which the QUIC protocol has associated with a QUIC
722 This is a new BIO method which is similar to a conventional BIO pair but
727 This is a new BIO API which allows a BIO to expose a poll descriptor. This API
733 This is a new BIO API which can be implemented by BIOs which implement datagram
741 to be enabled in which datagrams will not be silently truncated if they are
792 OpenSSL's QUIC implementation is designed to facilitate applications which wish
794 applications which wish to use the SSL APIs in a nonblocking fashion and manage
801 a structure which expresses some kind of OS resource which can be used to
807 Broadly, an application which wishes to manage its own event loop should
834 a L<BIO_s_datagram(3)>, or a custom BIO which implements
843 L<SSL_get_wpoll_descriptor(3)> to identify OS resources which can be used for
850 writability events on the underlying network BIO which was provided, and call