[Libevent-users] http input buffer deallocation problem

[Niels Provos]

On Mon, May 12, 2008 at 3:33 AM, Cezary Rzewuski
<C.Rzewuski at elka.pw.edu.pl> wrote:
>  I suspect there may be two reasons, but I don't know if this how libevent
> works:
>  1) there is any priority in events processed in libevent, and buffer
> deallocation remains in the tail of events queue
>  2) may be there is any HTTP header that causes libevent to postpone closing
> connection (which crawler uses but wget not).

We would have to see your code to figure out what's going on.  For
example, HTTP has persistent connections, i.e. connections that stay
open after a request has been handled.  It would also be good to know
which version of libevent you are using.

Niels.