Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by dug (2501) on 2005.02.17 8:26 (#38303) Journal
    I think it's great that you're working on IO::KQueue (and I think the name is fine, in the vein of IO::Select and IO::Poll).

    I've been quite happy with Event::Lib as a wrapper around various IO polling mechanisms (and although I don't use a system that supports kqueue, I hear libevent doesn't mind using it).

    Was there something keeping you from using Event::Lib? The external library dependancy? I'm just curious, and like to hear about the selection process from others.

    Congrats on settling in, I've been doing just that for about a year now [grin].
    • It's a number of things really - primarily that libevent is just more stuff than I need, and my code all integrates with Danga::Socket which uses low level calls to epoll/poll (and now kqueue) rather than going through another abstraction layer.

      Also I know some people more knowledgeable than I am about this stuff who don't have high opinions of libevent :-)