| /libuv/docs/src/ |
| H A D | async.rst | 7 Async handles allow the user to "wakeup" the event loop and get a callback
20 Type definition for callback passed to :c:func:`uv_async_init`.
36 Initialize the handle. A NULL callback is allowed.
45 Wake up the event loop and call the async handle's callback.
50 It's safe to call this function from any thread. The callback will be called on the
59 yield an execution of the callback. For example: if :c:func:`uv_async_send` is called 5
60 times in a row before the callback is called, the callback will only be called once. If
61 :c:func:`uv_async_send` is called again after the callback was called, it will be called
|
| H A D | timer.rst | 15 Example: a repeating timer with a 50 ms interval whose callback takes 17 ms
17 the timer callback runs as soon as possible.
28 Type definition for callback passed to :c:func:`uv_timer_start`.
50 If `timeout` is zero, the callback fires on the next event loop iteration.
51 If `repeat` is non-zero, the callback fires first after `timeout`
61 Stop the timer, the callback will not be called anymore.
72 to run on the given interval, regardless of the callback execution
77 If the repeat value is set from a timer callback it does not immediately take effect.
|
| H A D | prepare.rst | 7 Prepare handles will run the given callback once per loop iteration, right
20 Type definition for callback passed to :c:func:`uv_prepare_start`.
42 Start the handle with the given callback. This function always succeeds,
49 Stop the handle, the callback will no longer be called.
|
| H A D | check.rst | 7 Check handles will run the given callback once per loop iteration, right
20 Type definition for callback passed to :c:func:`uv_check_start`.
42 Start the handle with the given callback. This function always succeeds,
49 Stop the handle, the callback will no longer be called.
|
| H A D | poll.rst | 46 Type definition for callback passed to :c:func:`uv_poll_start`.
90 as an event is detected the callback will be called with `status` set to 0,
103 anyway, the callback *may* be called reporting an error status, but this is
114 will not be set on the `events` field in the callback.
118 callback will be called again, as long as the given fd/socket remains
122 * The callback has been called because the socket became
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
134 writable and hence the callback will be called again (depending on the
[all …]
|
| H A D | idle.rst | 7 Idle handles will run the given callback once per loop iteration, right
28 Type definition for callback passed to :c:func:`uv_idle_start`.
50 Start the handle with the given callback. This function always succeeds,
57 Stop the handle, the callback will no longer be called.
|
| H A D | fs_poll.rst | 24 The callback is invoked with `status < 0` if `path` does not exist
25 or is inaccessible. The watcher is *not* stopped but your callback is
29 When `status == 0`, the callback receives pointers to the old and new
31 callback only.
59 Stop the handle, the callback will no longer be called.
|
| H A D | migration_010_100.rst | 87 Allocation callback API change
90 In libuv 0.10 the callback had to return a filled :c:type:`uv_buf_t` by value:
98 In libuv 1.0 a pointer to a buffer is passed to the callback, which the user
144 Streams / UDP data receive callback API change
191 data on a pipe, which could also result in the reception of handles over it. The callback
205 the read callback:
|
| H A D | dns.rst | 82 callback will get called sometime in the future with the lookup result,
90 .. versionchanged:: 1.3.0 the callback parameter is now allowed to be NULL,
102 callback will get called sometime in the future with the lookup result.
105 .. versionchanged:: 1.3.0 the callback parameter is now allowed to be NULL,
|
| H A D | request.rst | 81 callback is called.
83 Here is how cancellation is reported to the callback:
89 callback invoked with status == `UV_ECANCELED`.
|
| H A D | stream.rst | 33 callback passed to ``uv_write`` is fired.
118 incoming connection is received the :c:type:`uv_connection_cb` callback is
128 When the :c:type:`uv_connection_cb` callback is called it is guaranteed that
138 Read data from an incoming stream. The :c:type:`uv_read_cb` callback will
149 Stop reading data from the stream. The :c:type:`uv_read_cb` callback will
187 The memory pointed to by the buffers must remain valid until the callback gets called.
235 operation will still be reported through a callback which is made
|
| H A D | signal.rst | 66 Type definition for callback passed to :c:func:`uv_signal_start`.
88 Start the handle with the given callback, watching for the given signal.
99 Stop the handle, the callback will no longer be called.
|
| H A D | design.rst | 32 - A prepare handle gets its callback called once every loop iteration when active.
33 - A TCP server handle that gets its connection callback called every time there is a new connection.
73 most part. There are cases, however, in which calling such a callback is deferred for the next
74 loop iteration. If the previous iteration deferred any I/O callback it will be run at this point.
101 get the close callback called.
|
| H A D | handle.rst | 57 Type definition for callback passed to :c:func:`uv_read_start` and
61 :c:type:`uv_read_cb` callback.
64 :c:type:`uv_udp_recv_cb` or the :c:type:`uv_read_cb` callback.
85 Type definition for callback passed to :c:func:`uv_close`.
140 arrival of the close callback.
|
| H A D | fs_event.rst | 116 Start the handle with the given callback, which will watch the specified
123 callback.
127 Stop the handle, the callback will no longer be called.
|
| H A D | udp.rst | 49 * must not be freed by the recv_cb callback.
54 * that it should now be freed by the recv_cb callback. When this flag is set
86 Type definition for callback passed to :c:func:`uv_udp_send`, which is
91 Type definition for callback passed to :c:func:`uv_udp_recv_start`, which
102 Can be NULL. Valid for the duration of the callback only.
110 those must not be freed. If no errors occur, there will be a final callback with
119 The receive callback will be called with `nread` == 0 and `addr` == NULL when there is
|
| H A D | errors.rst | 11 When a function which takes a callback returns an error, the callback will never
|
| H A D | tcp.rst | 88 ``UV_ETIMEDOUT`` error passed to the corresponding callback.
157 The callback is made when the connection has been established or when a
|
| /libuv/docs/src/guide/ |
| H A D | networking.rst | 31 3. Call ``uv_listen`` on the handle to have a callback invoked whenever a new
55 ``uv_listen`` is where we return to libuv's callback style. The second
58 When a connection is initiated by clients, the callback is required to set up
71 required. This can be done even in the ``uv_listen`` callback if you are not
79 callback of ``uv_listen`` is used by ``uv_tcp_connect``. Try::
92 callback receives the ``uv_connect_t`` struct, which has a member ``.handle``
137 Since UDP sockets are not connected to a particular peer, the read callback
194 ``getaddrinfo`` replacement [#]_. In the callback you can
206 your callback won't be invoked at all. All arguments can be freed immediately
209 callback can be ``NULL`` in which case the function will run synchronously.
[all …]
|
| H A D | basics.rst | 5 core job is to provide an event loop and callback based notifications of I/O
22 if there is a callback associated with e:
23 call the callback
191 only one callback) and usually indicates one I/O operation on a handle.
192 Requests are used to preserve context between the initiation and the callback
195 structure that is passed to the callback after the write is done.
205 implemented in the callback. For example, an IO watcher's callback will receive
206 the data read from a file, a timer callback will be triggered on timeout and so
212 Here is an example of using an idle handle. The callback is called once on
227 In callback based programming style you'll often want to pass some 'context' --
[all …]
|
| H A D | filesystem.rst | 21 callback is null. The return value of functions is a :ref:`libuv error code
23 The *asynchronous* form is called when a callback is passed and the return
50 void callback(uv_fs_t* req);
53 a callback for when the file is opened:
65 .. rubric:: uvcat/main.c - read callback
73 be filled with data before the read callback is triggered. The ``uv_fs_*``
86 will be triggered after the write is complete*. In our case the callback
90 .. rubric:: uvcat/main.c - write callback
245 allocate memory. In this case, the read callback is invoked with error
325 The callback will receive the following arguments:
[all …]
|
| H A D | threads.rst | 20 loop and callback principles, threads are complete agnostic, they block as
192 a task in a separate thread, and have a callback that is triggered when the
310 the loop is the receiver). libuv will invoke the callback (``print_progress``)
319 only guarantee that libuv makes is -- The callback function is called *at
321 calls to ``uv_async_send``, the callback won't be called. If you make two
322 or more calls, and libuv hasn't had a chance to run the callback yet, it
323 *may* invoke your callback *only once* for the multiple invocations of
324 ``uv_async_send``. Your callback will never be called twice for just one
372 1. In node, the third party library is set up with a JavaScript callback to be
388 callback, but cannot directly call into v8 to interact with JavaScript. So
[all …]
|
| H A D | utilities.rst | 12 Timers invoke the callback after a certain time has elapsed since the timer was
24 uv_timer_start(&timer_req, callback, 5000, 2000);
33 to stop the timer. This can be used safely from within the callback as well.
40 a timer callback, it means:
103 callback can be used to perform some very low priority activity. For example,
124 keep calling the idle callback again.
209 invoke the associated callback.
227 libcurl, we can register two callbacks. The socket callback ``handle_socket``
267 the callback is invoked.
273 ``UV_READABLE`` or ``UV_WRITABLE``. Now libuv will invoke the poll callback
[all …]
|
| /libuv/src/win/ |
| H A D | thread.c | 38 uv__once_cb callback; member
44 data->callback(); in uv__once_inner()
49 void uv_once(uv_once_t* guard, uv__once_cb callback) { in uv_once() argument
50 uv__once_data_t data = { .callback = callback }; in uv_once()
|
| /libuv/src/unix/ |
| H A D | thread.c | 453 void uv_once(uv_once_t* guard, void (*callback)(void)) { in uv_once()
454 if (pthread_once(guard, callback)) in uv_once()
|
