> Honest question: is there a purely event-driven I/O framework (no threads anywhere)? You might look into a continuation-based framework. With continuations,

> Honest question: is there a purely event-driven I/O framework (no threads anywhere)? You might look into a continuation-based framework. With continuations, you can do purely event-driven IO written in a direct style: the framework can grab the "callback" itself by snagging the continuation of its slow IO functions. You still run into the same problems with blocking (non-IO, or non-framework) code taking up more than its fair share of time, however.