Lines Matching refs:which
13 The [requirements for QUIC](./quic-requirements.md) which have formed the basis
63 libssl, which will support both blocking and non-blocking I/O.
99 - It is quite likely that there are buggy OSes out there which perform spurious
114 have a BIO interface which provides for select(3)-like functionality or which
131 - a thread which exists solely to execute blocking calls to the `BIO_write` of
133 - a thread which exists solely to execute blocking calls to the `BIO_read` of an
135 - a thread which exists solely to wait for and dispatch timeout events.
148 which require blocking semantics would only be able to function in thread
152 - Several threads are spawned which the application is not in control of.
164 such as the ACK Delay value, which is intended to describe the time between a
168 otherwise suboptimal performance will result. This is a usage model which
169 aligns optimally to non-blocking I/O and which cannot be accommodated
173 `BIO_write` calls, they will need to be adapted to support this, which is
180 - The question is posed of how to handle connection teardown, which does not
202 (notwithstanding the issues which preclude this noted above) for the purposes of
216 highly unlikely that any QUIC implementations exist which use blocking network
226 non-blocking mode. Though some OSes support a `MSG_DONTWAIT` flag which allows a
232 fewest disadvantages and is the only approach which appears to actually be
245 - Secondly, we have the option of providing a custom poller interface which
254 custom poller which synchronises using a custom poll descriptor based
320 than the current TLS stack, which cannot be used in blocking mode when used
350 - An FD which should be polled for readability, writability, or both; and
365 such as `BIO_dgram_pair` which do not naturally correspond to any OS primitive
366 which can be used for synchronisation, or when we are dealing with an
374 - A pollable BIO is a BIO which can provide some kind of OS-level
375 synchronisation primitive, which can be used to determine when
386 APIs on these platforms which have other handle spaces. However, this
393 for the purposes of this API, which will never return. Instead, the
403 synchronisation primitive which can be used to determine when the QUIC state
405 abstraction layer. Equivalent SSL object API calls which forward to the
435 Currently only a single descriptor type is defined, which is a FD on \*NIX and a
448 only useful when the application will provide a custom poller function, which
449 performs polling on behalf of libssl and which implements support for those
469 There are various circumstances which need to be handled:
475 The only limit comes when QUIC flow control (which only applies to
486 which is pollable, for example using condition variables. An application could
514 simpler for blocking applications, which are likely to be seeking a simpler
529 This will be implemented by an internal function which can accept up to two poll
530 descriptors (one for the read BIO, one for the write BIO), which might be
