[Libevent-users] multiple read events triggered

[Matt Pearson]

Please reply to the whole list in the future.

epoll actually supports (according to its man page) both this style of
notification and edge-triggered, where it tells you when a read is
first available and it's up to you to keep reading until read() fails
with errno = EAGAIN.  However, since not all notification mechanisms
support this kind of behavior, libevent uses the one that gives
consistent behavior across backends.  Besides, in many situations,
this kind of behavior is more useful.

On 10/2/07, Rick R <rick.richardson at gmail.com> wrote:
> Thanks for the heads-up on that. Do you happen to know if it's a feature of
> libevent alone, or is it a by-product of epoll specifically?