+1. Scheme seems inherently well-suited to this kind of model, esp.
given continuations and the plentiful supply of syntatic sugar.
(Reading Twisted code can be painful at times; I suspect that a Scheme
equivalent would bear much more readable and manageable code.)
This bears the question: is there anything comparable to the Twisted
framework (monolithic process with async IO, continuation-like
application design) in the Scheme world? Clearly the foundation is
there, I just wonder if anyone has "packaged the concept" as the
Twisted developers have.