Is the second argument to listen to limit the number of connect requests pending, or the total number of connections? I presume the former, since it certianly does not restrict the later with a LOCAL socket. Why/how could a program ever end up with such a queue, since a socket set to listen seems to "accept" a connection as the request is recieved?
Does this also mean that to truly limit the number of connections, a routine must exist to close them as soon as they are made beyond a certian number, or close the listening socket?