Re: [boost] Re: Sockets: proposal for a library design

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. 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. best regards William Lee _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜,带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有,搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆,雅虎电邮自助扩容! http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1...

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

On Tue, 15 Mar 2005 02:03:58 +0200, Boris <boris@gtemail.net> wrote:
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.
Great idea. It is not the case that iostreams-over-sockets might not be useful for some applications, they just shouldn't be the lowest layer of the implementation. -- Caleb Epstein caleb dot epstein at gmail dot com
participants (3)
-
Boris
-
Caleb Epstein
-
Willam Lee