" In his post, the caller passes itself as an argument (using a suitable interface type, of course), and the callee responds by invoking either a “found” or “not found” method on the caller."
Isn't this pretty much what you do in Twisted already?
the difference is that twisted uses trampolining - there's a top level scheduler that manages everything. if twisted worked exactly as described in this article then you'd run out of stack space (python doesn't eliminate tail calls) (also, of course, the trampoline allows other work to happen while processes yield, which is what makes twisted useful).
from another pov: this article describes how the designers of twisted want you to think (ie continuation passing style), but the actual implementation is slightly different.
Isn't this pretty much what you do in Twisted already?