On Tue, Oct 17, 2006 at 11:33:30PM -0000, Christopher Baus wrote: > > Has there been much interest in an IOCP port for libevent? I would > > certainly be interested. > > I even started working on a rough port, but as mentioned IOCP is proactive > > rather than reactive, > > (ie you tell it how much to read/send and the event tells you that) and it > > got rather awkward pretty quickly. > > The slickest implementation I've seen that works with *nix non-blocking > I/O and Windows IOCP is boost ASIO http://asio.sourceforge.net/. Instead > of modeling reactive behavior with IOCP, it mimics proactive behavior on > *nix. It works out surprisingly well.
I'm privy to my own [C] library which does this and more. Still, I don't think this necessarily belongs in libevent. libevent is popular because it does cross-platform event _polling_ very well, in a clean and simple interface. Integrating compound (higher-level) asynchronous actions like this is still a very fluid area. Take the recent DNS support in 1.2. It's probably going to follow the same tired path that c-ares, ADNS and UDNS have... slow and abortive patches for IPv6, SRV, CNAME, et al (granted UDNS has probably done the best out of all of them). libevent fills in its niche almost perfectly. If it starts to spill out all over the place things will only get messier; libevent originally made things cleaner. Maybe it's inevitable... I suppose that's how fluid areas become well trodden ground. _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
