I forgot to mention the other non-NI actor-oriented frameworks... helping you with AF may not be the right strategy... you might do better with LapDog or DQMH or one of the other async toolkits because of the difference in coding styles. As I've said several times: AF chose a particular set of priorities in its design: strict type safety, minimizing deadlock threat. Other toolkits had other priorities, like minimal developer time or speed of message throughput or... well, you get the idea. You can learn a lot by studying how the AF is put together and then adapt from there.
