Searched refs:callbacks (Results 1 – 14 of 14) sorted by relevance
/libuv/test/ |
H A D | benchmark-async-pummel.c | 31 static unsigned int callbacks; variable 40 if (++callbacks == NUM_PINGS) { in async_cb() 92 fmt(&fmtbuf[0], callbacks), in test_async_pummel() 94 fmt(&fmtbuf[1], callbacks / (time / 1e9))); in test_async_pummel()
|
/libuv/docs/src/ |
H A D | design.rst | 52 which have been added to the poller and callbacks will be fired indicating socket conditions 66 for a time before the loop's concept of *now* get their callbacks called. 72 #. Pending callbacks are called. All I/O callbacks are called right after polling for I/O, for the 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 95 for a read or write operation get their callbacks called at this point. 97 #. Check handle callbacks are called. Check handles get their callbacks called right after the 100 #. Close callbacks are called. If a handle was closed by calling :c:func:`uv_close` it will
|
H A D | loop.rst | 8 of polling for i/o and scheduling callbacks to be run based on different sources 127 there are no pending callbacks. Returns zero when done (no active handles 128 or requests left), or non-zero if more callbacks are expected (meaning 131 pending callbacks. Returns zero if done (no active handles 132 or requests left), or non-zero if more callbacks are expected (meaning 160 poll in one thread and run the event loop's callbacks in another see 191 You won't normally need to call this function unless you have callbacks
|
H A D | idle.rst | 15 Despite the name, idle handles will get their callbacks called on every loop iteration,
|
H A D | timer.rst | 7 Timer handles are used to schedule callbacks to be called in the future.
|
H A D | request.rst | 79 Cancelled requests have their callbacks invoked some time in the future.
|
H A D | migration_010_100.rst | 147 The streams and UDP data receive callbacks now get a pointer to a :c:type:`uv_buf_t` buffer,
|
H A D | handle.rst | 154 have their callbacks called asynchronously with status=UV_ECANCELED.
|
/libuv/docs/src/guide/ |
H A D | eventloops.rst | 28 ``stop_flag`` is set by ``uv_stop()``. Now all libuv callbacks are invoked 31 runs pending timer, idle and prepare callbacks, and invokes any pending I/O 32 callbacks. If you were to call ``uv_stop()`` in any of them, ``stop_flag``
|
H A D | basics.rst | 15 libuv, and the user can register callbacks to be invoked when an event occurs. 127 …or. Async functions that may fail will pass a status parameter to their callbacks. The error messa… 134 I/O read callbacks (such as for files and sockets) are passed a parameter ``nread``. If ``nread`` i…
|
H A D | filesystem.rst | 46 Filesystem operation callbacks have the signature: 88 callbacks. 261 unwrap it in the callbacks. We make a copy so we can free the two buffers from
|
H A D | utilities.rst | 102 The callbacks of idle handles are invoked once per event loop. The idle 227 libcurl, we can register two callbacks. The socket callback ``handle_socket``
|
H A D | networking.rst | 135 write callbacks will receive a status code of < 0 if something went wrong.
|
/libuv/ |
H A D | ChangeLog | 845 * zos: avoid fs event callbacks after uv_close() (Shuowang (Wayne) Zhang) 2408 * win, tty: remove zero-size read callbacks (Bartosz Sosnowski) 3552 * doc: clarify callbacks won't be called in error case (Saúl Ibarra Corretgé) 4271 * unix: make sure UDP send callbacks are asynchronous (Saúl Ibarra Corretgé) 5040 * unix: don't run i/o callbacks after prepare callbacks (Saúl Ibarra Corretgé) 5498 * windows: run close callbacks after polling for i/o (Saúl Ibarra Corretgé)
|
Completed in 39 milliseconds