You shouldn't be getting error conditions in this case. Remember, bufferevents are implemented using the underlying operating system's networking API, which typically will not alert you to errors except during a read, write, connect, or other similar network operation. If reading and writing are disabled, Libevent won't be doing network operations, so it can't notice errors.
On Thu, Nov 1, 2012 at 7:51 AM, Programmist Setevik < programmist.sete...@gmail.com> wrote: > When I call bufferevent_disable() on a bufferevent and disable both READ > and WRITEs, will I still get callbacks should there be an error condition > (say socket getting closed by peer) or no error conditions will be reported > for as long as I stay disabled in this fashion ? > > * > *
