Hey,
I understand Simon's view on how not to close buffer event sockets, but can
some one explain why this https://gist.github.com/714606 idea is bad?
-- Forwarded message --
From: Sid
Date: Wed, Nov 24, 2010 at 4:10 PM
Subject: Re: [Libevent-users] Closing bufferevents so
,
*const* *struct* evbuffer_cb_info *info, *void* *arg);
described http://www.wangafu.net/~nickm/libevent-book/Ref7_evbuffer.html
I think this is the right way to do this stuff...
On Wed, Nov 24, 2010 at 6:23 AM, Kelly Brock wrote:
> Hi Sid,
>
> > Sorry that got posted by mistake
Ok I am feeling that
*struct* evbuffer_cb_entry *evbuffer_add_cb(*struct* evbuffer *buffer,
evbuffer_cb_func cb, *void* *cbarg);
might be the solution to my problems...? Adding a calbaack to see how much
data is drained from the buffer??
On Tue, Nov 23, 2010 at 9:00 PM, Sid wrote
fer.
> So at this point i know exactly how much data to write. I need to reliably
> close this connection after all these bytes are out. How to achieve this?
>
> Sid
>
ll the evbuffer_add
only once for each line recieved and after that no more data will be written
to that specific o/p buffer.
So at this point i know exactly how much data to write. I need to reliably
close this connection after all these bytes are out. How to achieve this?
Sid
