Lines Matching full:bios

21   APIs; using custom network interaction BIOs in order to get the best
37  - We want to support custom BIOs on the network side and to the extent
38    feasible, minimise the level of adaptation needed for any custom BIOs already
48 over TCP. This will require applications using custom BIOs on the network side
49 to make substantial changes to the implementation of those custom BIOs to model
65 Blocking vs. Non-Blocking Modes in Underlying Network BIOs
69 used for the calls to the underlying network BIOs. To illustrate this point, we
75 the following events for the underlying network read and write BIOs immediately:
123 violating the BIO abstraction layer, and would not work with custom BIOs (even
172 - Since existing custom BIOs will not be expecting concurrent `BIO_read` and
174   likely to require substantial rework of those custom BIOs (trivial locking of
195   BIO and violates the BIO abstraction. For BIOs in general, there does not
199 need to change to using network BIOs with datagram semantics. For applications
200 using custom BIOs, this is likely to require substantial rework of those BIOs.
203 accommodating applications using custom network BIOs in a blocking mode, these
205 BIOs. In any case, it is expected to be comparatively rare that sophisticated
206 applications implementing their own custom BIOs will do so in a blocking mode.
249       BIOs, and therefore perform blocking I/O on top of any custom BIO.
251       For example, while historically none of our own memory-based BIOs have
269     - Applications will already have to make changes to any network-side BIOs,
271       BIO pair to a `BIO_s_dgram_pair`. Custom BIOs will need to be
333 at the libssl API level. Network-level BIOs must operate in a non-blocking mode
338 ### Support of arbitrary BIOs
340 We need to support not just socket FDs but arbitrary BIOs as the basis for the
358 This model is readily supported when the read and write BIOs we are provided
359 with are socket BIOs:
364 However, things become more complex when we are dealing with memory-based BIOs
369 ### Pollable and Non-Pollable BIOs
372 pollable and non-pollable BIOs.
382 #### Supporting Pollable BIOs  argument
455 underlying BIOs provided to the SSL object. For a socket BIO, this will likely
456 just yield the socket's FD. For memory-based BIOs, see below.
458 #### Supporting Non-Pollable BIOs  argument
527 `BIO_get_[rw]poll_descriptor` on the underlying BIOs and use a suitable OS
535 read and write BIOs, blocking mode cannot be enabled and blocking mode defaults