On Fri, Dec 3, 2010 at 4:28 PM, Evan Jones wrote:
[...]
>> Wow, good timing. I actually coded up an example patch to try to do
>> this earlier this week; have a look at branch "21_evloop_emptyok" in
>> my github repository [git://github.com/nmathewson/Libevent.git] and
>> see if it looks okay to
On Dec 3, 2010, at 15:47 , Nick Mathewson wrote:
A quick heads-up here that you'll want to know: there's a bug in
2.0.9-rc and earlier where activating an event from another thread
doesn't wake up the loop immediately. It should be fixed in 2.0.10;
see commit 5beeec9d43cb.
Yeah, I saw that one
On Fri, Dec 3, 2010 at 3:20 PM, Evan Jones wrote:
> I am writing a multi-threaded libevent application. Or rather, I am
> retrofitting an existing libevent 1.4 application to contain multiple
> libevent threads. Since the existing code is NOT thread safe, my design is
> basically to partition the
I am writing a multi-threaded libevent application. Or rather, I am
retrofitting an existing libevent 1.4 application to contain multiple
libevent threads. Since the existing code is NOT thread safe, my design
is basically to partition the application into N pieces, each with its
own event loop
