Hello, It will still be triggered. UV guarantees this.
Cheers, Fedor. On Sun, Feb 7, 2016 at 6:39 PM, Darren Smith <[email protected]> wrote: > Hi, > > I understand that uv_async_send() is the only/recommended way for a thread > to interact with another thread which is running the UV event loop. I.e., > thread A has called something like: > > uv_run(m_uv_loop, UV_RUN_DEFAULT); > > ... while thread B might do > > uv_async_send( h_async ); > > ...which prompts thread A to enter into the async callback (where it can > process events/data from B). > > Normally my application starts the uv_run first, and its only later that > calls to uv_async_send take place; it all works very well. > > However it is possible that my application (thread B) might make a call to > uv_async_send() before thread A has entered into the uv_run() call. For > these situations, where the async call is made before even the first call > into uv_run(), does UV guarantee to trigger the async callback. From quick > testing, it does appear that the async callback is made; but I wonder if > that is guarenteed by the underlying UV implementation. (I am using UV on > Linux). > > Thanks, > > Darren > > -- > 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 https://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
