Date: 2005-12-15 01:55:59
>When I was reading through the library tutorial half of examples there
>related to the synchronous IO. And, in all these examples a demuxer
>was used, that has nothing to do with synchronous IO. Do you think
>a clean interface? Do you think having to create and pass around an
>that is conceptially not required, is irrelevant?
I agree with Arkadiy.
Ideally boost should have a network library which wraps the OS depended
sockets APIs (hiding all differences between OS APIs). This library
should provide synchronous and asynchronous (aiocb, aio_read,
(asio mimics asynchronous io with synchronous io
(read,write,sento,recvfrom,...), select or poll or /dev/poll or epoll
On top of this networking library should be a demultiplexing library
which enables the user to implement services using the sockets and get
requests dispatched using the reactor pattern, proactor pattern or an
implementation of SEDA (would be the best) to the services in the
We need also a protocol stack library which can be used in the service
in order to implement application protocols.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk