Hi Boris,
I brought this as an example as I like the simplicity of asynchronous support in .NET and wanted to force Don to explain why he proposes a more complicated design. :) At least it seems to me more complicated (or let's say less intuitive) as I could understand asynchronous support in .NET quite fast but still have to ask for the exact meaning of Don's nexus and channel class.
I hope my previous message clarifies things a bit. The big difference between .NET and C++ is garbage collection. Many patterns/idioms that work well in a GC environment just don't work or get more complex, less intuitive, etc. in C++ where objects and data can be zapped while operations that were using them are still pending. Best, Don __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com