Lines Matching refs:handles
13 'handles' and 'streams' provide a high level abstraction for sockets and other entities;
28 handles and requests.
46 the loop or handles, for that matter) **is not thread-safe** except where stated otherwise.
53 (readable, writable hangup) so handles can read, write or perform the desired I/O operation.
69 when is a loop considered to be *alive*? If a loop has active and ref'd handles, active
70 requests or closing handles it's considered to be *alive*.
76 #. Idle handle callbacks are called. Despite the unfortunate name, idle handles are run on every
79 #. Prepare handle callbacks are called. Prepare handles get their callbacks called right before
87 * If there are no active handles or requests, the timeout is 0.
88 * If there are any idle handles active, the timeout is 0.
89 * If there are any handles pending to be closed, the timeout is 0.
94 in the previous step. All I/O related handles that were monitoring a given file descriptor
97 #. Check handle callbacks are called. Check handles get their callbacks called right after the
98 loop has blocked for I/O. Check handles are essentially the counterpart of prepare handles.