Re: [boost] asio formal review begins

From: Oliver.Kowalke_at_[hidden]
Date: 2005-12-15 01:55:59

Hi,

>When I was reading through the library tutorial half of examples there
were
>related to the synchronous IO.  And, in all these examples a demuxer
object
>was used, that has nothing to do with synchronous IO.  Do you think
this is
>a clean interface?  Do you think having to create and pass around an
object,
>that is conceptially not required, is irrelevant?
>Arkadiy

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,
aio_write,...) io
(asio mimics asynchronous io with synchronous io
(read,write,sento,recvfrom,...), select or poll or /dev/poll or epoll
and threads).
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
application.
We need also a protocol stack library which can be used in the service
in order to implement application protocols.

Oliver