Caleb Epstein wrote:
On Fri, 18 Mar 2005 18:03:50 -0500, Edward Diener <eddielee@tropicsoft.com> wrote:
Obviously Boost has a thread library, although I have not used it, and it has a callback mechanism in boost::function<> which I have used extensively, so designing an asynchronous I/O library around these two concepts seems like a good design to me.
I'd say coupling asynchronous I/O to multi-threading would be a mistake. It is at its most useful IMHO in single-threaded cases.
I just want to add this link which has a very good overview about how asynchronicity works in .NET: http://blogs.msdn.com/cbrumme/archive/2003/05/06/51385.aspx It explains the four ways to do asynchronous operations in .NET: 1) callback 2) polling for completion 3) waiting for completion 4) calling the asynchronous operation a second time and then wait (somehow comparable to waiting for completion) Boris