From: SourceForge.net <no...@so...> - 2011-07-03 02:02:40
|
Bugs item #3350045, was opened at 2011-07-02 22:02 Message generated for change (Tracker Item Submitted) made by nickm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=461322&aid=3350045&group_id=50884 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: libevent-core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Mathewson (nickm) Assigned to: Nobody/Anonymous (nobody) Summary: bufferevent_pair should keep event_base alive. Initial Comment: If the only active thing in an event_base is a bufferevent_pair, the event_base will exit. This is because paired buffervents don't use any events internally, so they don't stop the event loop from reaching its "no events pending" condition and exiting. Arguably, paired bufferevents _should_ keep the event loop from exiting. If anyone's interested in fixing this in bufferevent_pair.c, the way to go is probably to look at the internal functions "event_base_add_virtual" and "event_base_del_virtual" in event.c. A "virtual" event serves no purpose other than to keep the event base from exiting. The rule to implement is probably something like, "Add a virtual event whenever a paired bufferevent has reading enabled, or whenever it has writing enabled and has data to write." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=461322&aid=3350045&group_id=50884 |