Lines Matching full:connections

33 entity which listens for incoming connections. It is **not** intended to be QUIC
36 accepting incoming TCP connections easy.
45 collectively for all connections created by that listener.
73 supporting non-blocking network I/O which our SSL API for QUIC connections has
137  * ensure it has started to accept incoming connections but does not wish to
166 `SSL_CTX` is intended to span the lifespan of multiple TLS connections there is
180 ### Notes on Internal Refactoring to Support Multiple Connections
199 With server operation, multiple connections will share a single UDP
218 A listener allows multiple connections to be received on a UDP socket. However,
221 to create a QLSO, use it to accept connections, and also use it to initiate
222 outgoing connections.
247 API even if it is only initiating connections as a client and never accepting
248 connections. There are several reasons why an application might want to do this:
251 - it allows the application to handle the TERMINATING phase of connections in a
263 application exceeds the lifetime of most client connections. The listener can
265 terminating and terminated connections, even if (as far as the application is
266 concerned) no client connections currently exist and all prior client
267 connections have been freed using `SSL_free`. The internal `QUIC_CHANNEL` can be
281 incoming connections. A client can then use `SSL_new_from_listener` as usual to
287 support multiple outgoing client connections on one socket these will need to
496 - A server QLSO can also make outgoing client connections.
499   it is assumed to be uninterested in accepting connections and this implies the