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

From: Iain.Hanson_at_[hidden]
Date: 2002-02-28 14:06:47

Author:  davlet.panech (davlet_panech_at_[hidden]) at unix,mime
Date:    28/02/02 17:51

     
>I think if we are providing a constructor that takes a sockaddr, we 
>might as well provide the inverse of that.

The constructor that takes a sockaddr is there for calls to accept. I 
don't know of any use case that supports the inverse except to be 
able to use the address class with the C api. This is not something I 
wish to support unless someone can show3 compelling reasons for it.

     
>That's OK, I just think that this 1st abstraction layer (aka BSD 
>socket wrapper) shouldn't be hard-wired into the upper layers. IMHO 
>it's not that hard to do (we just need to make sure that our upper 
>layers are parametrized properly); yet it will allow us to use the 
>upper layers with non-socket-based networking. 

Here I agree with you. I suspect that ACE did not find its common 
IPC abstraction until after the first light weight wrappers had been 
created. I suspect that when sockets has been completed we may well 
see similarities that would allow a framework to build.

I appreciate the constructive comments. Thanks.

/ikh

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.