libuv的多线程之间传递消息.docxVIP

libuv的多线程之间传递消息Inter-thread communicationSometimes you want various threads to actually send each other messages?while?they are running. For example you might be running some long duration task in a separate thread (perhaps using?uv_queue_work) but want to notify progress to the main thread. This is a simple example of having a download manager informing the user of the status of running downloads.progress/main.c 1 2 3 4 5 6 7 8 9101112131415uv_loop_t *loop;uv_async_tasync;int main() { loop = uv_default_loop();uv_work_treq;int size = 10240;req.data = (void*) size;uv_async_init(loop, async, print_progress);uv_queue_work(loop, req, fake_download, after); return uv_run(loop, UV_RUN_DEFAULT);}The async thread communication works?on loops?so although any thread can be the message sender, only threads with libuv loops can be receivers (or rather the loop is the receiver). libuv will invoke the callback (print_progress) with the async watcher whenever it receives a message.WarningIt is important to realize that the message send is?async, the callback may be invoked immediately after?uv_async_send?is called in another thread, or it may be invoked after some time. libuv may also combine multiple calls to?uv_async_send?and invoke your callback only once. The only guarantee that libuv makes is – The callback function is called?at least once?after the call to?uv_async_send. If you have no pending calls to?uv_async_send, the callback won’t be called. If you make two or more calls, and libuv hasn’t had a chance to run the callback yet, it?may?invoke your callback?only once?for the multiple invocations of?uv_async_send. Your callback will never be called twice for just one event.progress/main.c 1 2 3 4 5 6 7 8 91011121314void fake_download(uv_work_t *req) {int size = *((int*) req-data);int downloaded = 0; double percentage; while (downloaded size) { percentage = downloaded*100.0/size;async.data = (void*) percentage;uv_async_send(async); sleep(1);