On Dec 21, 2010, at 12:29 , Mark Ellzey wrote:
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*.
Well, there were bugs in it until recently. A
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 bec
On Dec 21, 2010, at 10:44 , Mark Ellzey wrote:
There are other options for consumer/worker pools. Check out
https://strcpy.net/mark/evthreads/ which uses a per-thread base
you can defer functions into threads from your main base.
You can do this with libevent 2.0, using thread-safe event loops,
On Sat, Dec 18, 2010 at 08:31:23PM -0500, Kevin Bowling wrote:
> One of the ideas I saw floating around for libevent 2.1 was threaded event
> bases to ease thread pool programming.
>
> This seems like a pretty challenging project and probably beyond my
> abilities at the moment but if we can hash
One of the ideas I saw floating around for libevent 2.1 was threaded event
bases to ease thread pool programming.
This seems like a pretty challenging project and probably beyond my
abilities at the moment but if we can hash some specs out I'd be interested
in helping see it through to completion.
