Jorge Godoy wrote:
How do you expect to connect and handle all that traffic without using a
different TCP port for each client? This is the same that happens with
(x)inetd and several other daemons.
When you receive a connection at the specified port, the software forks and
then opens a connection in another port, and keep on listening the original
port for new incoming connections.
Wait a minute. I'm not sure what limitations CherryPy/Http 1.0 have,
but it is perfectly OK to have multiple *connections* to the same port.
It's even OK to have multiple connections to the same port from the same
remote host. Only 1 server can *listen* on a particular port, however.
-Steve
