>Yes, it’s certainly true that what we actually want is connect_to_name, not >resolve_name_to_address+connect_to_address. Right. But connect_to_name is just what SOCKS does. I agree that SOCKS has its problems, but in this case its API is pretty good for name-that-is-not-in-the-DNS-for-service-that-is-not-TCP. Even if we posit a cleaner connect_to_name than SOCKS, and an extended nsswitch.conf that handles mappings from names to libraries that implenent various non-TCP transports, we're still back to the question of where does the list of names and libraries come from. R's, John