On Thu, Sep 06, 2012 at 11:30:54PM +0200, Joachim Bauch wrote:
> Thanks for the heads up. The socket-based code surely will be helpful
> when the implementation starts. I wrote an initial draft of how the
> API could look like and put it on github:
> https://github.com/fancycode/Libevent/blob/buf
Hi experts,
While setting socket FD in event loop, should FD be set non-blocking (using
fcntl)?
Further I am confused about how to use libevent and would really appreciate
some technical inputs on below.
I am in a process of designing multi-threaded application and would like a
main thread - a
On Thu, Sep 6, 2012 at 3:19 PM, Venkatesh Solaiyappan
wrote:
> Hello:
>
> In one of our system, CPU hogs in one of the thread whose stack trace to
> the following:
> Wondering if it is a known issue?? Pls advise.
>
>
>
> #0 0x7fe60a5ef4c0 in ?? () from /usr/lib64/libevent-2.0.so.5
>
> #1 0x
On Thu, Sep 6, 2012 at 6:58 PM, Roman Puls wrote:
[...]
> event-dump-lock.patch for the latter
> event-foreach-fully.patch for the first topic (public API). However, I
> generally changed the signature of the callback to const (struct
> event_base|event).
Thanks, Roman!
I just merged the heavy-
