Lines Matching refs:callback
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``)
315 It is important to realize that since the message send is *async*, the callback
318 multiple calls to ``uv_async_send`` and invoke your callback only once. The
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
344 The callback is a standard libuv pattern, extracting the data from the watcher.
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
391 4. The async callback, invoked in the main loop thread, which is the v8 thread,
392 then interacts with v8 to invoke the JavaScript callback.
