Dennis,

> Data packets may not care what they contain, but the addressing
> is crucial. Servers wait on KNOWN ports for clients

I know.   But you are going fully outof scope I'm afraid.

Also, I think you missed the part where I describe that both 'puters connect
to the Pi - The Pi does *not* connect to the 'puters - and *especially not*
to random ports.

> This is where your "A connects to B", "C connects to B", and now
> data flows falls apart. Especially if "A" connects to "B" twice (say
> twodifferent programs want to transfer different data to "C"). Both
> connections are made to the single server port on "B". How does
> "C" make two connections to "B" and /somehow/ identify WHICH
> connection from "A" it means expects (or vice versa, if "C" makes to
> connections to "B", how does "A" identify which one it wants to connect
> with).

:-) That single port access is not intended for random programs to connect
to.  Just /my/ program, which transfers whatever I like to another of /my/
programs receiving it on the other side.

But, if I ever want to have random programs on one side to connect to random
programs on the other side (which is exactly what I *don't* want !)  than I
could imagine starting a "connection" with a single block of data indicating
the intended target - perhaps implementing something like the "ports" scheme
TCP/IP already has .... :-)

Regards,
Rudy Wieser

--- SoupGate-Win32 v1.05