2014-08-01 10:44 GMT+02:00 Saúl Ibarra Corretgé <[email protected]>: > If you have a timer that kicks in 100ms, UV_RUN_ONCE will block for > 100ms. What I showed was an example.
Same as if you close the timer in its first callback (and that is even better than using UV_RUN_ONCE since you can free the timer handle and the entire loop without having to iterate all of them and call uv_close for later run again uv_run to execute their close callbacks). >> If there is no real use-cases for UV_RUN_ONCE (that cannot be achieved >> with UV_RUN_DEFAULT and/or UV_RUN_NOWAIT) then I suggest dropping it. >> > > Not going to happen. People embedding libuv into other event loops may > want to iterate the loop at their own pace. UV_RUN_DEFAULT doesn't help > because it will loop for ever, and UV_RUN_NOWAIT doesn't help either > because it always does a zero tiemout poll. > > The fact that *you* don't need it doesn't mean other don't have a use > for it. That's why I was asking. -- Iñaki Baz Castillo <[email protected]> -- 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.
