Firing the callback and getting the result asynchronously

[Globik]

Is this operation an analog of uv_queue_work() function? If yes, should it work with last commit and without uv_async_send?

[kroggen]

It is similar.

The uv_queue_work() uses a worker thread pool and we don't need to configure them.

The asynchronous call in uv_callback calls the function from another single thread that has its own loop.

We use the last option when we set the app with more than a single thread loop and we have the control to which thread the call will be made.

[Globik]

Thank you for reply @kroggen , now I understand.
I've tried uv_callback in conjuction with uv_queue_work() (is it a bad practice?) with the same loop for both. Surprisingly for me I've found it works. (Without uv_async_send(&async) of course) . I've merked also that the uv_callback's callbacks are firing an event just like in node.js EventEmmiter().emit('my_event', data) does in a single thread loop.

But by now I didn't yet figured out all features of this approach. Just a little hello_world.c with uv_queue_work() and uv_callback all together I've written for me.