On Sat, Aug 27, 2011 at 11:47 PM, Anibal Monsalve Salazar <anibal@debian.org> wrote:
No; I don't think I've seen these before. Also, there is no new
development happening on Libevent 1.4.x. The stable release series is
2.0.x; new features are being added to 2.1.x. I would only do a new
Libevent 1.4 release in the event that a critical security bug were
found. I would definitely not accept patches into Libevent 1.4 to
implement new features!
Looking at the patches, they seem to divide into two broad areas:
* Disabling the "timeval cache" feature in the main event loop... by
commenting it out. This is already doable in Libevent 2.0 using a
run-time configuration option that turns it off on a per-program
basis. Look at the EVENT_BASE_FLAG_NO_CACHE_TIME option. There's
also been a thread on the libevent-users list about future directions
in this area; see
http://archives.seul.org/libevent/users/Aug-2011/msg00011.html and
subsequent comments for possible directions.
* Adding some new features to evhttp. Some of it looks interesting
and possibly generally of general utility, and getting a patch for
inclusion into Libevent 2.1 there would be grand; some of it looks
like stuff that you can already do in Libevent 2.0 and later with
other interfaces. (See for example evhttp_bind_listener.)
cheers,