|
Boost : |
From: Boris (boris_at_[hidden])
Date: 2005-03-14 19:03:58
Willam Lee wrote:
> A C++ framework for network is very useful and long
> for. I have seen the ACE, but felt it too weight. The
> proposed library seems a lightweight one and the
> socket wrapper is appropriate.
> I think if user manage the sockets one by one, the
> proposed library will work perfectly. But in common
> network applications, a server usually serves on
> several sockets or ports with a select() style
> function. In this condition, how to process multiple
> socket class for different connection the proposal ?
> In the pseudo code, select() function is a member
> function of socket, maybe it can only process the
> 'this' socket.
You are right: The signature of socket::select() as you have seen it in the
Wiki is not complete.
> Finally I don't like build socket lib based on
> iostream, but the net lib can provide some operator
> like "<<" , ">>" to simulate the iosteam-style
> calling.
>
> Thanks Boris's work.
Thanks for your comments, too! After reading many times that I/O streams are
not desired on a low level I will update my proposal and move I/O streams
support to a higher level.
Boris
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk