Got, Thank you.
2011/11/25 Nick Mathewson
> On Thu, Nov 24, 2011 at 8:49 PM, 李永平 wrote:
> > Hi all,
> > I found a blemish in the struct evbuffer, which has a member: parent.
> The
> > testing libevent is 2.0.15.
> > when i tried to get the "parent" bufferevent from evbuffer, like below:
> >
On Thu, Nov 24, 2011 at 8:49 PM, 李永平 wrote:
> Hi all,
> I found a blemish in the struct evbuffer, which has a member: parent. The
> testing libevent is 2.0.15.
> when i tried to get the "parent" bufferevent from evbuffer, like below:
> #include "event2/event.h"
> #include "event2/b
Hi all,
I found a blemish in the struct evbuffer, which has a member: parent. The
testing libevent is 2.0.15.
when i tried to get the "parent" bufferevent from evbuffer, like below:
#include "event2/event.h"
#include "event2/buffer.h"
#include "event2/bufferevent.h"
//...
On Thu, Nov 24, 2011 at 12:34 PM, Nick Mathewson wrote:
> I tidied the documentation a little in a44cd2b0205df; and fixed a
> couple of robustness issues in f3b89dec9eac2cf: you might want to
> check those out to make sure I didn't mess it up for you.
Still works fine here, thanks!
***
On Mon, Nov 21, 2011 at 8:06 PM, Catalin Patulea wrote:
> By default, allow_dirty_shutdown is 0, reporting
> TCP-close-before-SSL-close as BEV_EVENT_ERROR.
>
> But many https servers out there do dirty shutdowns, so clients need
> to be able to set this flag.
>
> This patch simply adds a getter/se
On Mon, Nov 21, 2011 at 8:04 PM, Catalin Patulea wrote:
[...]
> bev_ssl currently only reports EVENT_EOF when the connection is
> closed, so it confuses evhttp. This patch makes bev_ssl additionally
> set one of BEV_EVENT_{READING|WRITING}, as appropriate, when the
> connection is closed.
The pat
