bev_async_consider_reading/writing call the eventcb directly about libevent HOT 6 CLOSED

bev_async_consider_writing has this same problem. It really seems like the event callbacks for these two cases should be deferred. It's pretty hard to plan for evbuffer_add deleting the bufferevent out from under you.

from libevent.

I agree. Is this something you can do a patch for, or should I look into it? The 2.1 ACTIVE_LATER framework might make this easier to implement, but would require more infrastructure changes on bufferevents in general.

from libevent.

I don't have experience with the deferred callback system in libevent yet, so you might have an easier time of it.

from libevent.

Hm, this could be fixed with BEV_OPT_DEFER_CALLBACKS, no?

from libevent.

Actually there is a check against bev_async->ok, so it mustn't call bev_async_consider_reading

from libevent.

I'm closing this, since there is a unit test that passes, please reopen if you will find problems.

from libevent.