Am 06.09.2012 17:44, schrieb Nick Mathewson:
On Thu, Sep 6, 2012 at 8:40 AM, Roman Puls wrote:
Hi Nick,
excellent - it would be even greater to specify a callback procedure
receiving the struct event tokens (I currently write language bindings for
tcl, and it would be great to generate the tex
Hi,
I want use libevent as timer management tool in our program. Our program is
multi-thread , and each thread will use some timer.
I can enter into the call back function after I called the following
functions: event_assign(), event_add(), event_base_dispatch() , it
works fine.
But I notice
-Ursprüngliche Nachricht-
Von:Nick Mathewson
[...]
> Sounds like a big but fun project. You might want to look at
> bufferevent_sock.c first; bufferevent_openssl.c has to jump through a
> lot of annoying hoops because the TLS protocol has a property that
> doing a read at the TLS abst
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 0x7fe60a5efa7f in evmap_io_add () from /usr/lib64/libevent-2.0.so.5
#2 0x00
Hi Nick,
Thanks for the response. Here is a follow up.
The evhttp_make_request procedure is used several times on the same
connection (http persistance). In this case, is the request structure freed
when I make a new request using the same connection? I do not own the
request. After several reque
On Thu, Sep 6, 2012 at 1:13 PM, Bruno Avila wrote:
> Hi,
>
> Once I make an evhttp request (e.g. GET) and read the content from the
> evbuffer, which buffers of struct evhttp_request should I free? Or is done
> transparently by libevent?
When the request is freed, its buffers should get freed too
Hi,
Once I make an evhttp request (e.g. GET) and read the content from the
evbuffer, which buffers of struct evhttp_request should I free? Or is done
transparently by libevent?
Thanks,
Bruno
On Thu, Sep 6, 2012 at 8:40 AM, Roman Puls wrote:
> Hi Nick,
>
> excellent - it would be even greater to specify a callback procedure
> receiving the struct event tokens (I currently write language bindings for
> tcl, and it would be great to generate the textual representation myself)
Hm. This w
Hi Nick,
excellent - it would be even greater to specify a callback procedure
receiving the struct event tokens (I currently write language bindings
for tcl, and it would be great to generate the textual representation
myself)
But why I write:
shouldn't that stuff (event_base_dump_events) b
