Re: sockets Interface for address class

From: davlet_panech (davlet_panech_at_[hidden])
Date: 2002-03-01 09:18:43

--- In boost_at_y..., jk_at_s... wrote:
> 27 Feb 2002 23:51:25 +0300 Hamish Mackenzie wrote:
> >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.
> 
> Not all types of addresses are network addresses with port numbers,
> service names etc. There is "unix domain" address type in unices, 
and
> the address itself is just a pathname somewhere in file tree. 
Obviously,
> such an address doesn't require any resolving, and still it is
> absolutely usable address for socket binding etc. (if the socket 
itself
> created as "unix domain" type socket).

Yes, and in general we shouldn't make any assumptions about the 
representation of an address, so each protocol (or protocol family) 
would probably have it's own address class (which could be something 
as simple as string -- say, for "UNIX domain" sockets or WinNT pipes).

D.P.

> 
> -- 
> jk