| /libuv/docs/src/ |
| H A D | idle.rst | 7 Idle handles will run the given callback once per loop iteration, right
8 before the :c:type:`uv_prepare_t` handles.
11 The notable difference with prepare handles is that when there are active idle handles,
15 Despite the name, idle handles will get their callbacks called on every loop iteration,
|
| H A D | design.rst | 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*.
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
[all …]
|
| H A D | loop.rst | 99 has finished executing and all open handles and requests have been closed,
123 referenced handles or requests. Returns non-zero if :c:func:`uv_stop`
124 was called and there are still active handles or requests. Returns
127 there are no pending callbacks. Returns zero when done (no active handles
131 pending callbacks. Returns zero if done (no active handles
139 Returns non-zero if there are referenced active handles, active
140 requests or closing handles in the loop.
197 Walk the list of handles: `walk_cb` will be executed with the given `arg`.
232 On Mac OS X, if directory FS event handles were in use in the
235 implementation. Instead, uses of directory FS event handles in
[all …]
|
| H A D | pipe.rst | 7 Pipe handles provide an abstraction over streaming files on Unix (including
27 Only a connected pipe that will be passing the handles should have this flag
41 passing the handles should have this flag set, not the listening pipe
140 Set the number of pending pipe instance handles when the pipe server is
149 Used to receive handles over IPC pipes.
168 Create a pair of connected pipe handles.
170 The resulting handles can be passed to `uv_pipe_open`, used with `uv_spawn`,
177 This is recommended for handles that will be used by libuv,
|
| H A D | handle.rst | 12 Libuv handles are not movable. Pointers to handle structures passed to
14 care when using stack allocated handles.
202 This function works for TCP, pipe and UDP handles on Unix and for TCP and
203 UDP handles on Windows.
219 This function works for TCP, pipe and UDP handles on Unix and for TCP and
220 UDP handles on Windows.
229 The following handles are supported: TCP, pipes, TTY, UDP and poll. Passing
278 active `and` referenced handles left. The user can force the loop to exit early
279 by unreferencing handles which are active, for example by calling :c:func:`uv_unref`
285 All handles are referenced when active by default, see :c:func:`uv_is_active`
|
| H A D | fs_poll.rst | 7 FS Poll handles allow the user to monitor a given path for changes. Unlike
8 :c:type:`uv_fs_event_t`, fs poll handles use `stat` to detect when a file has
9 changed so they can work on file systems where fs event handles can't.
|
| H A D | stream.rst | 7 Stream handles provide an abstraction of a duplex communication channel.
134 `server` and `client` must be handles running on the same loop.
166 /* Logic which handles the write result */
192 Extended write function for sending handles over a pipe. The pipe must be
214 handles over a pipe like c:func:`uv_write2`.
242 Currently only works on Windows for :c:type:`uv_pipe_t` handles.
243 On UNIX platforms, all :c:type:`uv_stream_t` handles are supported.
|
| H A D | poll.rst | 7 Poll handles are used to watch file descriptors for readability,
10 The purpose of poll handles is to enable integrating external libraries that
17 It is possible that poll handles occasionally signal that a file descriptor is
22 It is not okay to have multiple active poll handles for the same socket, this
31 On windows only sockets can be polled with poll handles. On Unix any file
|
| H A D | migration_010_100.rst | 187 Receiving handles over pipes API change
191 data on a pipe, which could also result in the reception of handles over it. The callback
204 handles using :c:func:`uv_pipe_pending_count` and :c:func:`uv_pipe_pending_type` while in
|
| H A D | prepare.rst | 7 Prepare handles will run the given callback once per loop iteration, right
|
| H A D | check.rst | 7 Check handles will run the given callback once per loop iteration, right
|
| H A D | udp.rst | 7 UDP handles encapsulate UDP communication for both clients and servers.
242 Get the remote IP and port of the UDP handle on connected UDP handles.
243 On unconnected handles, it returns `UV_ENOTCONN`.
385 For connected UDP handles, `addr` must be set to `NULL`, otherwise it will
388 For connectionless UDP handles, `addr` cannot be `NULL`, otherwise it will
417 For connected UDP handles, `addr` must be set to `NULL`, otherwise it will
420 For connectionless UDP handles, `addr` cannot be `NULL`, otherwise it will
|
| H A D | tcp.rst | 7 TCP handles are used to represent both TCP streams and servers.
178 The resulting handles can be passed to `uv_tcp_open`, used with `uv_spawn`,
185 This is recommended for handles that will be used by libuv,
|
| H A D | fs_event.rst | 7 FS Event handles allow the user to monitor a given path for changes, for example,
52 Event types that :c:type:`uv_fs_event_t` handles monitor.
|
| H A D | process.rst | 7 Process handles will spawn a new process and allow the user to control it and
245 Disables inheritance for file descriptors / handles that this process
247 this process don't accidentally inherit these handles.
|
| H A D | async.rst | 7 Async handles allow the user to "wakeup" the event loop and get a callback
|
| H A D | timer.rst | 7 Timer handles are used to schedule callbacks to be called in the future.
|
| H A D | signal.rst | 7 Signal handles implement Unix style signal handling on a per-event loop bases.
|
| /libuv/test/ |
| H A D | test-ipc-send-recv.c | 35 union handles { union
49 union handles send;
50 union handles send2;
51 union handles recv;
52 union handles recv2;
61 union handles recv;
62 union handles recv2;
94 union handles* recv; in recv_cb()
308 union handles* recv; in read_cb()
|
| H A D | benchmark-getaddrinfo.c | 33 static uv_getaddrinfo_t handles[CONCURRENT_CALLS]; variable
75 getaddrinfo_initiate(&handles[i]); in BENCHMARK_IMPL()
|
| H A D | runner-win.c | 181 HANDLE handles[MAXIMUM_WAIT_OBJECTS]; in process_wait() local
191 handles[i] = vec[i].process; in process_wait()
199 result = WaitForMultipleObjects(n, handles, TRUE, timeout_api); in process_wait()
|
| H A D | test-fs-event.c | 413 uv_fs_event_t* handles = handle->data; in timer_cb_watch_twice() local
414 uv_close((uv_handle_t*) (handles + 0), NULL); in timer_cb_watch_twice()
415 uv_close((uv_handle_t*) (handles + 1), NULL); in timer_cb_watch_twice()
|
| /libuv/docs/src/guide/ |
| H A D | basics.rst | 189 Handles represent long-lived objects. Async operations on such handles are
213 every turn of the event loop. A use case for idle handles is discussed in
229 handles and requests have a ``void* data`` member which you can set to the
|
| /libuv/ |
| H A D | Makefile.am | 209 test/test-loop-handles.c \
239 test/test-poll-multiple-handles.c \
331 test/test-walk-handles.c \
|
| /libuv/.github/workflows/ |
| H A D | CI-win.yml | 60 # https://github.com/libuv/leps/blob/master/005-windows-handles-not-fd.md
|
