This shows up in evhttp. You don't get the socket closed notification once
the headers have been read and the socket has had READ disabled unless you
write more data. Is there a way to fix this in evhttp?
On Thu, Nov 1, 2012 at 6:39 AM, Nick Mathewson wrote:
> You shouldn't be getting error co
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
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 ?
*
*
