Lines Matching full:would

23   handling, using fibres). Would prefer to use the existing APIs - they don’t
25   would be willing to make minor changes.
84 Blocking on all three wakeup conditions listed above would require use of an API
122 trying to implement QUIC on top of blocking I/O in this way would require
123 violating the BIO abstraction layer, and would not work with custom BIOs (even
129 parallel threads. Under this model, there would be three threads:
141 would coordinate and synchronise with these background worker threads via
148   which require blocking semantics would only be able to function in thread
150   desired, our APIs would only be usable in a non-blocking fashion.
204 applications would still have to completely rework their implementation of those
217 I/O, as (as mentioned above) it would lead to suboptimal performance due to the
248       powerful and would allow the application to implement its own pollable
262       particularly difficult, though providing custom pollers here would mean
280       non-blocking mode, it would need to be trying to use the socket in some
304     interface, the application would actually be able to exercise more control
501 Moreover this would undermine the BIO abstraction.