Cool, good to know. Thanks for the prompt response. MY
On Monday, March 31, 2014 2:57:15 PM UTC-6, Fedor Indutny wrote: > > Hello! > > Honestly saying, this is not in our plans. libuv here is providing some > primitives for scheduling a work to the worker threads, but the rest is to > be provided by your application. > > Cheers, > Fedor. > > > On Tue, Apr 1, 2014 at 12:37 AM, booch > <[email protected]<javascript:> > > wrote: > >> Currently the threadpool work queue from threadpool.c and the async work >> queue on the uv loop are boundless. Are there any backlog plans to address >> some kind of resource limitations around these queues? >> >> Cheers, >> MY >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] <javascript:> >> . >> Visit this group at http://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 http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
