July 24, 2001
4:29 a.m.
it doesn't bother anyone else that you deal with unix sockets through something named "tcp.Port"? "TCP" has quite a specific meaning, after all, and unix sockets are neither dependant on nor a subset of TCPness... My first impulse would be to rename the tcp module to 'socket', but that would probably b0rk stuff horribly due to collisions with the standard 'socket' module. -- "The naming of hosts is a serious matter, not just one of your holiday games..." -- RFC 2100, "The Naming of Hosts"