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

Simo Sorce simo at redhat.com
Tue Aug 23 09:42:05 EDT 2011


On Tue, 2011-08-23 at 09:23 -0400, Tom Yu wrote:
> 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.

I guess you'll need to list dependencies and licenses and see which one
fits better.

> Also, it's not NIH; I want something minimal that won't cause us much
> additional maintenance overhead if we bundle it.

Which means yet another library to get right, fix bugs, add features
every time you want to use another, handle issues on different
platforms, etc..  Sounds like a lot of work for very little gain.

>   As far as I can
> tell, all other portable event loop libraries have more dependencies,
> support multiple kernel file descriptor monitoring interfaces, etc.

I guess you can more easily strip out options than create everything
from scratch ?

> 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.

I'd just like to avoid wasting precious time on coding yet another event
loop. But if you think that's easier than taking an existing one and
strip out the unnecessary bits go for it.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York




More information about the krbdev mailing list