Lines Matching refs:on
11 rely on the event loop to signal it about the socket status changes, like
14 more scalable than what can be achieved with :c:type:`uv_poll_t`, especially on
91 and the detected events set on the `events` field.
106 then call :c:func:`uv_close` on the handle.
109 Calling :c:func:`uv_poll_start` on a handle that is already active is
113 Though `UV_DISCONNECT` can be set, it is unsupported on AIX and as such
114 will not be set on the `events` field in the callback.
123 readable/writable and the callback did not conduct a read/write on
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
130 :c:func:`uv_poll_start` on a poll handle associated with this socket,
134 writable and hence the callback will be called again (depending on the
