Lines Matching refs:socket
11 rely on the event loop to signal it about the socket status changes, like
22 It is not okay to have multiple active poll handles for the same socket, this
27 but it might also start polling another socket. However the fd can be safely
79 .. c:function:: int uv_poll_init_socket(uv_loop_t* loop, uv_poll_t* handle, uv_os_sock_t socket)
81 Initialize the handle using a socket descriptor. On Unix this is identical
84 .. versionchanged:: 1.2.2 the socket is set to non-blocking mode.
102 not close the socket while the handle is active. If the user does that
118 callback will be called again, as long as the given fd/socket remains
122 * The callback has been called because the socket became
124 this socket at all.
125 * The callback committed a read on the socket, and has not read all the
127 * The callback committed a write on the socket, but it remained
129 * The socket has already became readable/writable before calling
130 :c:func:`uv_poll_start` on a poll handle associated with this socket,
131 and since then the state of the socket did not changed.
133 In all of the above listed scenarios, the socket remains readable or
147 callback is also canceled, even if the socket state change notification
