From: Don G (dongryphon_at_[hidden])
Date: 2005-04-12 09:41:34
I've posted a zip with an HTML file and an HPP file that describes an
abstract way to interact with the network. It is intended as a medium
level interface. By that I mean it is above the socket layer, but
below buffering/proactor/reactor kinds of thinking. It is really a
pure C++ way to interact with the primitive concepts of networking.
In the proposal I posted, work is done by worker threads. User code
interacts with these to do async/non-blocking operations (see the
HTML for details). What is missing is the pure async library that
would allow trivial marshalling of such callbacks back to a single
thread. I will look at putting that piece together with usage
examples in the next couple days to round out the interface proposal.
I am curious to know what folks think about this approach.
I believe the code recently posted by Michel André is complementary
in the sense that it is a way to connect implementation details such
as stream/datagram with how I/O blocking is performed. That said,
there is a fundamental difference in what the user of the library
would see and have to handle. It may just be me, but I am not a fan
of the coupling created by explicitly connecting multiple I/O objects
with a dispatcher. This is a tedious prospect. Especially when there
are limits on the number of such connections a dispatcher can handle
(such as 64-ish for Windows).
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk