On Sun, Feb 22, 2015 at 8:36 AM, Devchandra Meetei <[email protected]> wrote: > That's right. I am with you. I never said that are asynchronous. > Just curious what will be the best way to dealt in such scenario to make it > asynchronous. > May be this is not related to libuv also. But wanted to get some expert > advice on such scenario. > Please forgive me for asking non libuv related questions on libuv list.
Sorry, I missed your reply. If you want to break up an operation into asynchronous pieces, you can use an uv_idle_t. The 'idle' in uv_idle_t is a bit of a misnomer: the callback fires repeatedly as long as it's active, not just when the event loop is idle. We copied the name from libev but we didn't end up implementing the libev semantics. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
