If this turned out to be a real bug, I made a change that might help:
[hz...@dev066 libevent-1.4.11-stable]$ svn diff
Index: http.c
===
--- http.c (revision 184899)
+++ http.c (working copy)
@@ -1976,6 +1976,8 @@
evhttp_s
Shouldn't you call evhttp_send_reply_end in the callback of
evhttp_send_reply_chunk which is only called if the sending succeeded?
On 9/4/09, Haiping Zhao wrote:
> Hi, there,
>
> I'm reading evhttp's source code, and I'm not sure if I've found a bug, or I
> just mis-read it. But it seems to me
Hmm, that should help. I have several send_reply_chunk() though. Are you
suggesting they should form nested callback chains?
-Haiping
On 9/4/09 3:19 PM, "q6Yr7e0o nIJDVMjC" wrote:
Shouldn't you call evhttp_send_reply_end in the callback of
evhttp_send_reply_chunk which is only called if the s
Hi,
> Hmm, that should help. I have several send_reply_chunk() though. Are you
> suggesting they should form nested callback chains?
Afaik it's the only threadsafe way of ensuring to not call reads and
writes on already closed descriptors. Although i know it's highly
unportable i use gcc's neste