On Nov 28, 2005, at 1:58 PM, Jorge Godoy wrote:
Bob Ippolito <[EMAIL PROTECTED]> writes:
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.
How can you get to answer to 2 simultaneous clients on the same
port at the
same time without multicast/broadcast then? Threads allow you to run
concurrent things but they don't magically turn your physical
medium into
something that can carry more information at the same time.
TCP connections are uniquely identified by a source and a
destination. Only one piece of information needs to differ in order
for it to be a separate connection. In this case, we're talking
IPv4, so for each location there's 32 bits of IP address and 16 bits
of port... so each connection is uniquely identified by all 96 bits.
In the given netstat at the beginning of this thread, there was one
listening connection (which has no source), and all the other
connections had the same source IP (127.0.0.1) but differed in source
port.
-bob
