On Tue, 2010-06-01 at 12:24 +0900, hcpark wrote:
> I used
> bufferevent_free(bev);
Right. Silly me.
Felix
***
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-usersin the body.
Hey.
What's the "suggested" way to close a bufferevent connection?
Currently I do:
fd = bufferevent_getfd(bev);
evutil_closesocket(fd);
... followed by a manual:
my_event_handler(bev, BEV_EVENT_EOF, NULL);
... because it doesn't seem to be called otherwise.
Is this th
Hi.
While working on an HTML-escaping filter for my evhttp_send_reply_html()
something came to me...
The purpose of evhttp is to build something around a really minimalistic
httpd, possibly in the embedded world; so you want to report error
messages beyond the HTTP status code - and on the other
On Wed, 2010-05-26 at 13:50 -0400, Nick Mathewson wrote:
> > If you have no objections, feel free to apply it.
> Done, with minor tweaking to make it C90-compliant.
Great. Sorry about the C99 thing - why don't you add the appropriate
compiler switch to the build system? Wouldn't have happened then
Forwarding this discussion from Bug #3006553 to the ML:
First of all, I've attached a new version of my patch to this Mail -
this one just allows NULL reasons for evhttp_response_code and changes
evhttp_send_error to display the actual reason. I did not however change
the parameter semantics from
