Hi
I've run into an issue and I'm wondering if it's expected behavior or not.
If a bufferevent with a configured read-high-watermark actually reaches the
watermark, the TCP disconnect on the underlying socket is not reported. I've
observed this on Mac OS X (kevent) as well as linux 3.5 (epoll
Have you accounted for the possibility of clients falling off the map / buffers
overflowing ?
Can you reduce the code to the simplest possible example that reliably
demonstrates the problem and post it somewhere ?
On 2012-05-08, at 7:48 AM, Shahid wrote:
> I have been using libevent in all m
On 2011-06-24, at 10:57 PM, Nick Mathewson wrote:
> Tentatively, I'm going to blame this one on some kind of buffering or
> stalling issue in netcat or in your terminal, not on libevent. When I
> write a trivial libevent-based client program to hammer your server
> program, it works fine. See t
Hi everyone
I'm trying to keep a hostile client from causing a libevent server from
consuming too much memory in buffered data.
Using bufferevents, I let libevent keep the input buffer within limits using
its watermark mechanism, and I added a simple mechanism in the server to,
essentially, s
