On Tue, Dec 21, 2010 at 11:02:25AM -0500, Evan Jones wrote: > You can do this with libevent 2.0, using thread-safe event loops, > and using event_active() to "trigger" an event to be run in another > thread.
I've never had much luck with event_active across multiple threads, though this may be because of my own ignorance. This also does not tell the thread *what* to do, just that it needs to do *something*. If you feel as if you want that thread to do everything after it's been queued, never to return to the parent, then that is a fine solution - but it really limits the abstractions in your code. *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe libevent-users in the body.
