Re: [boost] Re: sockets Interface for address class

From: Iain.Hanson_at_[hidden]
Date: 2002-03-01 12:42:40

Ahhh. Now I think I understand where the confusion is comming from. The 
requirements state that we need to restrict ourselves to the network and 
transport layers and not go off into http and ftp.

I have no desire to go against this requirements but IP is not the only network 
layer protocol that is supported by the C sockets API.

I would like to reproduce, as much as possible, of the genericity of the C 
sockets API with type saftey and without some of the redunancy.

/ikh

______________________________ Reply Separator _________________________________
Subject: Re: [boost] Re: sockets Interface for address class
Author:  davlet.panech (davlet_panech_at_[hidden]) at unix,mime
Date:    01/03/02 14:58

--- In boost_at_y..., "Dale Peakall" <dale.peakall_at_b...> wrote: 
> 
> I thought that we'd sort of decided that what we were writing here 
> was a TCP/IP library, not sockets in the more general sense.
> 
> If you're going to start going down the multi-protocol route, then 
> things really start getting complex.
> 
     
I don't think we are going to support anything besides TCP (and 
possibly UDP), all I'm saying we should try to keep our design 
flexible to allow for extensions.
     
> Things are complex enough as they are.  Do you try and support 
> asynchronous communications?  
     
Some people fell strongly about supporting async operations (although 
I personally do not mind dropping this).
     
D.P.
     
     
     
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.