Christian Huitema wrote:
Actually this is nitpicking. The *real* problem is that the systems need a "connect me to this host*name*" system/library call, that will handle all the underlying combinations and do the right thing, depending on system preferences and capabilities.Do you mean something like WSAConnectByName (http://msdn2.microsoft.com/en-us/library/ms741557.aspx)? Or maybe "TcpClient.Connect (String, Int32)" (http://msdn2.microsoft.com/en-us/library/system.net.sockets.tcpclient.connect.aspx)?
Or something like: https://java.sun.com/j2se/1.4.2/docs/api/java/net/Socket.html#Socket(java.lang.String,%20int) TCP is trivial to do.Providing the same capability for applications that use UDP is harder, since one would have to involve the application to get feedback whether a particular IP address worked or not; TCP gets this from the SYN|ACK without application involvement.
Erik