[RFC][PATCH] krb5 => libverto main loop

[Tom Yu]

Simo Sorce <simo at redhat.com> writes:

> Just bundle an existing one, don't NIH please.

Which one would you recommend bundling?  It looks like the smallest
event loop library might be libev, but I haven't done a thorough
comparison.

Also, it's not NIH; I want something minimal that won't cause us much
additional maintenance overhead if we bundle it.  As far as I can
tell, all other portable event loop libraries have more dependencies,
support multiple kernel file descriptor monitoring interfaces, etc.

By choosing a single interface -- probably select(), or poll() if we
believe that poll() is better and that nobody who wants to build our
code from source needs to build on a system that lacks poll() -- we
can keep code size and complexity down.  We can change course and
bundle a small existing library instead, if it turns out that the
effort of rolling our own highly constrained event loop becomes
significant.  (I doubt that it will unless we go beyond a single
interface.)

What I'm envisioning doesn't need to have the same performance or
features of an existing event loop library; it just has to be no worse
than what we have right now in the pre-libverto world.  I hope that
people who need more performance will not find it too much trouble to
build and use an existing event loop library for use with libverto.