Hi Nick! Thanks for answering!
>Ugh. It looks like you're running into EVBUFFER_MAX_READ, defined in
>buffer.c . You can edit the source and redefine it as high as you
>want, but there's no way to change it programmatically right now. I'd
>love to make the "how much to read or write" logic mor
Hi,
Writing this in between errands.
> > Just a note before the details. I would suggest adding a little
> > section to the manual covering the proper method of handshaked shutdown.
> > It's just a minor thing but figuring out the watermark method is non-
> obvious
> > till you gi
On Sat, Oct 30, 2010 at 11:55 AM, Kelly Brock wrote:
> Hi Nick,
[...]
> Just a note before the details. I would suggest adding a little
> section to the manual covering the proper method of handshaked shutdown.
> It's just a minor thing but figuring out the watermark method is non-obvious
On Sat, Oct 30, 2010 at 12:03 PM, Ralph Castain wrote:
> Just wondering: would it make sense to provide a libevent API for this?
Yes, what kind of API did you have in mind? The easiest would be
something to implement bufferevent_flush(BEV_FINSISHED) for sockets,
and define it to a) write as much
Just wondering: would it make sense to provide a libevent API for this?
I ask because proper shutdown is important to a number of us, and it seems a
shame that we all have to independently sprinkle the code throughout our
programs wherever sockets are used. On the surface, at least, it would app
Hi Nick,
> > Ok, so figured out a way to do this and it seems clean and works with
> the
> > select based backend but not the iocp based backend. Basically I just
> set
> >
> > But, it does not seem to work on the IOCP version which seems a bit odd
> > since this should be handled at the OS level
