Re: [boost] Re: sockets library

From: Iain.Hanson_at_[hidden]
Date: 2001-12-20 12:54:42

Thats the plan.

/ikh

______________________________ Reply Separator _________________________________
Subject: [boost] Re: sockets library
Author:  allan (allan_at_[hidden]) at unix,mime
Date:    20/12/01 17:28

From: Iain.Hanson_at_[hidden]
>
> Efficientcy is not the only reason that iostreams are not suitable for the 
> loewest layer of a C++ networking library. They do not map well onto any 
of the
> packet oriented protcols such as those build on UDP. 
>
> ASCII protocols are far from in the majority either standardosed or 
propriarty.
>
> IMHO efficiency, functionality, and type-saftey are all key issues in the 
lowest
> layer of a network programming library.
     
I'm usually a Boost lurker but this one is close to my heart.
     
I understand and accept the arguments made about not basing a sockets layer 
on streamio, streambuf and friends.  I think Ross is right.
     
However, I can also appreciate the convenience of using sockets like any 
other stream.
     
Would it not be possible to write two libraries?
- the first would be the non stream based, efficient library that Ross and 
others would like to see.
- the second would build on top of this and provide the stream based i/o.
     
Yes, there would be a cost in terms of performance for the stream stuff but 
this would be left user-developer to decide.
(If you are doing lots of text based i/o you probably prefer streams, and if 
your doing a lot of text based i/o efficiency probably isn't your number on 
concern.)
     
Just an idea.
     
allan
     
     
     
Info: http://www.boost.org  Send unsubscribe requests to: <mailto:boost-unsubscr
ibe_at_[hidden]> 
     
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
     
     

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.