On Sun, 21 Sep 2014 18:17:04 +0200, Sönke Ludwig wrote:

It uses the event loop implementation specific mechanism - for libevent
that is event_base_loopbreak and for Win32 it's a WM_QUIT message.

What I don't exactly understand is why can't we also use that mechanism for the "temporary implicit event loop for each blocking operation"?

Is it because vibed does not have a reference to those event loops?
Is it because if we quit one temporary event loop we would just continue to the next one, once we reach the next blocking operation in the module ctor?