[Libevent-users] multiple read events triggered

[Scott Lamb]

Matt Pearson wrote:
> 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.

I remember seeing a while ago a patch that would optionally use the 
other behavior.

Not sure if it ever made it to this list, but google finds it elsewhere:

https://webmail.iro.umontreal.ca/pipermail/gambit-list/2005-August/000367.html

if "event_abilities() & EV_ABILITY_EDGE" is true, you could use 
EV_READ|EV_WRITE|EV_PERSIST|EV_EDGE or the like.