Re: [boost] sockets Interface for address class

From: Iain.Hanson_at_[hidden]
Date: 2002-02-28 08:32:27

As I posted previously, This is more the job of a resolver class and could 
also be layered on top of this address class as a resolvable_address.

There as sufficent occasions when you know that a DNS lookup is not 
required to warrant supporting efficient construction of an address.

I like using DNS names in applications that I write and so a good resolver 
class will also be needed.

/ikh

______________________________ Reply Separator _________________________________
Subject: Re: [boost] sockets Interface for address class
Author:  boost (boost_at_[hidden]) at unix,mime
Date:    27/02/02 20:40

On Wed, 2002-02-27 at 18:47, Iain.Hanson_at_[hidden] wrote:
>      The following is the interface for a unicast address in psudo code. 
>      I'm not that enamoured by the names of the mutator and accessor 
>      methods so if anyone has better suggestions they would be welcome. I'd 
>      appreciate comments, is this interface complete ? is it too fat? etc.
     
I think a general purpose address class should store the arguments 
required to look up an address using "getaddrinfo". This means
1) It sould store a service name instead of the port.
2) It should also contain an addrinfo containing the hints. 
     
The getaddrinfo could then be wrapped in two classes address_info_list 
and address_info.
     
Hamish
     
     
     
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.