Lines Matching refs:a
7 Stream handles provide an abstraction of a duplex communication channel.
30 this type. When a stream is in non-blocking mode, write requests sent
37 Callback called when data was read on a stream.
41 the `buf` parameter might not point to a valid buffer; in that case
53 The buffer may be a null buffer (where `buf->base` == NULL and `buf->len` == 0)
58 Callback called after data was written on a stream. `status` will be 0 in
63 Callback called after a connection started by :c:func:`uv_connect` is done.
68 Callback called after a shutdown request has been completed. `status` will
73 Callback called when a stream server has received an incoming connection.
109 Shutdown the outgoing (write) side of a duplex stream. It waits for pending
110 write requests to complete. The `handle` should refer to a initialized stream.
117 connections the kernel might queue, same as :man:`listen(2)`. When a new
124 connections. Call this function after receiving a :c:type:`uv_connection_cb`
152 This function is idempotent and may be safely called on a stopped stream.
169 uv_buf_t a[] = {
183 uv_write(&req1, stream, a, 2, cb);
192 Extended write function for sending handles over a pipe. The pipe must be
196 `send_handle` must be a TCP, pipe and UDP handle on Unix, or a TCP
197 handle on Windows, which is a server or a connection (listening or
202 Same as :c:func:`uv_write`, but won't queue a write request if it can't be
214 handles over a pipe like c:func:`uv_write2`.
216 Try to send a handle is not supported on Windows,
231 Enable or disable blocking mode for a stream.
235 operation will still be reported through a callback which is made
