On Nov 28, 2005, at 1:38 PM, Jorge Godoy wrote:
Steve Bergman <[EMAIL PROTECTED]> writes:
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.
Then you either multiplex the connection or fork it to another port.
You are very confused. Forking and sockets have nothing to do with
each other. In the CherryPy case, it isn't even forking, it's
threads. You should read up on TCP instead of confusing everyone else.
What's happening here is that CherryPy isn't eagerly closing down the
TCP sockets as quickly as Apache is apparently doing. No more, no
less. If the connections were to remain open with Apache you'd see
20 connections from 20 different origin ports. CherryPy is only
LISTENING on one port, just like Apache. This is almost definitely
harmless, but it's probably worth taking a look into seeing why
they're staying alive... it might just be HTTP Keep-Alive with a more
optimistic timeout than what Apache is using.
-bob
