Lines Matching refs:SSL_write
21 - [`SSL_write`, `SSL_write_ex`](#-ssl-write----ssl-write-ex-)
237 #### `SSL_write`, `SSL_write_ex`
334 any data which was appended to the stream via `SSL_write` may or may not have
339 via `SSL_stream_conclude`), data appended to the stream via `SSL_write` will
410 non-partial-write `SSL_write` operation spanning multiple `SSL_write` calls,
577 process begins. This ensures that where an application which calls `SSL_write`
581 flag, in which case any data appended to streams via `SSL_write` (or any
584 data written to streams via `SSL_write` is no longer relevant. Application
662 Any data already queued for transmission via a call to `SSL_write()` will still
666 the stream via calls to `SSL_write`. Further attempts to call `SSL_write` after
751 * and that future calls to SSL_write will fail.
1137 * consumption. `SSL_read` and `SSL_write` calls must be made on a QUIC
1142 * operation for single-stream usage. If `SSL_write` is called before the
1145 * remotely-initiated stream before the local application calls `SSL_write`
1148 * unidirectional, calls to `SSL_write` will fail. Attempts to create
1155 * local application calls `SSL_write` prior to the peer creating a
1159 * to `SSL_write` (with `len > 0`), that stream will be bound as the default
1437 `SSL_write` always waits until all data is written unless an error occurs. The
1438 semantics of `SSL_write` are preserved unchanged.
1440 **Q. Does `SSL_write` block until data is written to the network, or simply
1443 A. `SSL_write` blocks until it has accepted responsibility for the data passed
1621 As such, an application which calls `SSL_write` on a QUIC connection SSL object
1624 We can use the ordering of initial calls to `SSL_read` and `SSL_write` to infer
1627 Supporting locally-initiated streams (`SSL_write` called first) is simple;
1652 - The local application calls `SSL_write()` (`len > 0`). A locally-initiated
