[17141] in Kerberos_V5_Development
Re: [RFC][PATCH] krb5 => libverto main loop
daemon@ATHENA.MIT.EDU (Nico Williams)
Wed Sep 7 22:30:46 2011
MIME-Version: 1.0
In-Reply-To: <ldvobzg45z9.fsf@cathode-dark-space.mit.edu>
Date: Wed, 7 Sep 2011 21:30:40 -0500
Message-ID: <CAK3OfOiZuarZykRJmkS5irwfkO34mJBW4sYYCdiND8O8pLLtKQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tom Yu <tlyu@mit.edu>
Cc: Ken Raeburn <raeburn@mit.edu>, "krbdev@mit.edu" <krbdev@mit.edu>,
Simo Sorce <simo@redhat.com>
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Tue, Aug 23, 2011 at 8:23 AM, Tom Yu <tlyu@mit.edu> wrote:> Simo Sorce <simo@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.
Why bundle? Just make one a requirement and let the user building MITkrb5 deal with it. But if you must bundle, then bundle libevent --libevent is supported on all the platforms mentioned so far.
> 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.
Implementing and maintaining a portable backend will be much harderthan just bundling a portable backend.
Nico--
_______________________________________________krbdev mailing list krbdev@mit.eduhttps://mailman.mit.edu/mailman/listinfo/krbdev
