Lines Matching full:network

21   APIs; using custom network interaction BIOs in order to get the best
22   performance at a network level as well as OS interactions (IO handling, thread
37  - We want to support custom BIOs on the network side and to the extent
39    in use on the network side. More generally, the integrity of the BIO
45 Note that implementation of QUIC will require that the underlying network BIO
48 over TCP. This will require applications using custom BIOs on the network side
54 events as well as the circumstances where a network socket becomes readable or
62 network. This is independent of and orthogonal to the application interface to
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
70 first consider how QUIC might be implemented using blocking network I/O
75 the following events for the underlying network read and write BIOs immediately:
77 - The underlying network write BIO becomes writeable;
78 - The underlying network read BIO becomes readable;
85 such as select(3) or poll(3), regardless of whether the network socket is
109   multi-threaded network I/O on the backend.
112 directly but uses the BIO abstraction to access the network, so these issues are
132   an underlying network BIO,
134   underlying network BIO,
176   on network I/O simultaneously).
182   and `BIO_write` calls on some underlying network BIO, there needs to be some
199 need to change to using network BIOs with datagram semantics. For applications
203 accommodating applications using custom network BIOs in a blocking mode, these
211 network side makes satisfying our requirements for QUIC easy, and also allows
216 highly unlikely that any QUIC implementations exist which use blocking network
225 This approach in general requires that a network socket be configured in
269     - Applications will already have to make changes to any network-side BIOs,
291       simply sharing a network socket, as incoming datagrams will not be routed
313   - Does not require an application-provided network-side custom BIO to be
333 at the libssl API level. Network-level BIOs must operate in a non-blocking mode
406 equivalent calls of the underlying network BIO will also be provided.
437 changes needed on different platforms in the common case of an OS network
462 application will handle its own network I/O, for example via a
471   - The QUIC implementation wants to write data to the network but
479   - The QUIC implementation wants to read data from the network