On Thu, Jul 06, 2006 at 02:50:07PM -0500, Vijay K. Gurbani wrote: > Folks: I have not looked into the internals of libevent, but I > presume that it uses normal APIs like read() and write() to do > I/O. How hard would it be to modify it to use recvmsg() instead? > Has anyone done it? I am interested in getting ancillary data > present in a IP header through the recvmsg() API. >
libevent proper does no I/O. It only does readiness notification on descriptors. The buffering API has read/write hardcoded, unfortunately. But if you're reading UDP datagrams (which I recvfrom(2) suggests), then you hardly need just simple stream buffering (if you need buffering at all), and libevent event notifications is all you'll need. - Bill _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
