On Mon, Jul 2, 2012 at 4:23 AM, Avi Bab wrote:
>
> I am using libevent-2.0.18-stable running on Linux (CentOs 6.2) to implement
> an HTTP proxy.
> For each connection I define: (i) an edge-triggered read event and (ii) a
> socket-based bufferevent with EV_WRITE enabled and EV_READ disabled.
Rig
On Jul 5, 2012, at 4:20 PM, Nick Mathewson wrote:
> On Thu, Jul 5, 2012 at 3:34 PM, Scott Dorr wrote:
>> When an event_del() is called on an evq, what happens to triggerings that
>> were already 'in-flight' but haven't had their callbacks called yet.
>
> event_del() will make an active event in
On Thu, Jul 5, 2012 at 3:34 PM, Scott Dorr wrote:
> When an event_del() is called on an evq, what happens to triggerings that
> were already 'in-flight' but haven't had their callbacks called yet.
event_del() will make an active event inactive; if its callback was
scheduled but has not been run,
When an event_del() is called on an evq, what happens to triggerings that were
already 'in-flight' but haven't had their callbacks called yet.
For example:
read event R is active on fd 42, uses 'callback_func()' as its callback
new packet P1 comes in on fd 42
new packet P2 comes in on fd 42
libe
