>>Does that include win32 IOCPs (io completion ports) yet?
>>If not, they're definitely worth a look. However, they're not very
>>"selecty", in that they scale well and they tell you when something
>>has actually happened instead of when something might happen without
>>blocking, maybe. I don't know how well that would fit in with libevt.
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.
It might be worth finding some way to wrap the IOCP structures in a module/class that behaves a little more like standard sockets so it would be easier to integrate.....
_______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
