[17106] in Kerberos_V5_Development
Re: [RFC][PATCH] krb5 => libverto main loop
daemon@ATHENA.MIT.EDU (Sam Hartman)
Tue Aug 23 16:00:37 2011
From: Sam Hartman <hartmans@mit.edu>
To: Tom Yu <tlyu@mit.edu>
Date: Tue, 23 Aug 2011 16:00:28 -0400
In-Reply-To: <ldv4o195ayb.fsf@cathode-dark-space.mit.edu> (Tom Yu's message of
"Mon, 22 Aug 2011 18:38:04 -0400")
Message-ID: <tslvctnew4j.fsf@mit.edu>
MIME-Version: 1.0
Cc: Ken Raeburn <raeburn@mit.edu>, "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Tom" == Tom Yu <tlyu@MIT.EDU> writes:
Tom> Greg Hudson <ghudson@MIT.EDU> writes:
>> (As for the issue at hand, I will take charge of doing what we
>> reasonably can to minimize the pain of relying on an external
>> event loop, but I'm not sure exactly what that is yet.)
Tom> I wonder how difficult it would be to create (and bundle) a
Tom> small event loop back end for libverto that implements the bare
Tom> minimum of functionality that we would use in our code. To
Tom> keep this from expanding into another fully-featured event
Tom> library, we could constrain it to using only select() for file
Tom> descriptor events, for example.
Tom> _______________________________________________ krbdev mailing
Tom> list krbdev@mit.edu
Tom> https://mailman.mit.edu/mailman/listinfo/krbdev
I agree with Simo.
Please bundle something, do not create your own.
Supporting things beyond select is quite important; you need something
that does more than 1024 fds at a minimum.
But really, you actually want a real event library.
Pick one of the many options you have.
My preference is libevent, but I'm happy with whatever.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
