Hi!
> You would have to be prepared to handle a change to the fd at basically
> any time, including a change to no fd.
Excuse me my ignorance I didn't know that it was so complex.
Now I realize that when libev has to tear things down and rebuilds everything
from scratch in effort to cure after fo
On Fri, May 02, 2014 at 01:19:42AM +0400, Nick Zavaritsky
wrote:
> There is one thing that still bothers me: now it takes two epoll_wait() calls
> for Nginx to fetch the events
> instead of one. (One epoll_wait() in libev plus another epoll_wait() for the
> nested epoll fd maintained
> solely b
Hi!
I realy love the flexibility and the great design of libev, however I am a bit
puzzled with the
event loop embeding.
The problem is that I want to mix and match code that uses libev event loop
with the code
tailored for a very different event loop environment, all in the same thread.
This
