Lines Matching full:calls

69 used for the calls to the underlying network BIOs. To illustrate this point, we
90 calls to send(3) or recv(3) may block for some arbitrary period of time, meaning
128 Another conceptual possibility is that blocking calls could be kept ongoing in
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
138 `BIO_write` calls do not take an excessive amount of time.
161 - By blocking in `BIO_write` calls, this precludes correct implementation of
173   `BIO_write` calls, they will need to be adapted to support this, which is
175   calls obviously does not work since both of these calls must be able to block
182   and `BIO_write` calls on some underlying network BIO, there needs to be some
183   way to force these calls to return once `SSL_free` is called and we need to
314     reworked to support concurrent calls to it.
379     primitive, but its state only changes in response to calls made to it (or to
405 abstraction layer. Equivalent SSL object API calls which forward to the
406 equivalent calls of the underlying network BIO will also be provided.
465 When libssl calls `BIO_get_[rw]poll_descriptor` on the underlying BIO, the call
467 calls `SSL_get_[rw]poll_descriptor`, that call also fails.
476     application stream data) applies a limit; then calls to e.g. `SSL_write` we
482     Here calls like `SSL_read` need to fail with `SSL_ERROR_WANT_READ`; we