For the '--with-libev' option, I concur.
The benchmark numbers look appealing compared to libevent:
http://libev.schmorp.de/bench.html
Is it compatible with ALv2 (I'm not a lawyer but my review of libev's
LICENSE file looks like it is)?
What is libev's maturity level (actively maintained; adding features;
maintenance mode; no changes for over 1 year)?
Is this change involved enough to warrant its own branch?
Is libevent effectively its only competitor? I noticed liboop but it's
LGPL; and glib Main Event Loop but that's GPL or LGPL. Is that it?
Should we start a wiki page if this be an involved decision? Perhaps
this change is too trivial?
Cheers,
Andrew
Leif Hedstrom wrote:
How about we take a two-step approach here? My worry is to break
something major like this int he first week of being OpenSource. So, my
suggestion is:
1) We add a --with-libev configure option.
2) If this option is not specified, we use the existing epoll() code
on Linux.
3) On other platforms, the --with-libev becomes implicit (since
there's no other choice anyways)
Later on, we can decide if libev becomes default on all platforms, but
at least this way we have some options. Thoughts?
