From: Iain Hanson (Iain.Hanson_at_[hidden])
Date: 2005-04-01 09:11:52
On Fri, 2005-04-01 at 13:53 +0300, Boris wrote:
> While asynchronicity in .NET is basically based on threads it is not true
> for asynchronous I/O. If you built asynchronous I/O on top of an
> asynchronicity library with callbacks in threads you will end up with 1000
> threads blocked in read() if you have 1000 sockets.
No. This would be a configuration or implementation detail. The only
requirement is that you have at least 1 thread dispatching async
requests and queueing work to be dispatched. LibC AIO has an init
function where the user can supply a hint regarding size of thread pool
to use. I think the contract for a C++ lib should be stronger and allow
the user to specify/control the size of the thread pool as well as the
type of the ACT ( not just callback, but signal and polling ).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk