capi wrote: |
Likewise, it makes no sense for two different processes to share the same port on the same machine. That would make it impossible for that machine's operating system to know to which process it should send incoming data on that port. Remember, the whole reason of a port number is to uniquely identify a process on a given machine. |
neewt wrote: |
I feel this needs some further clarification, because many times, processes do sort of share a single port for connection establishment and sometimes even communication. Linux's Inetd is one example of such an implementation, were it multiplexes services by forwarding incoming connections to the "correct" binary. I am not hundred procent sure, but TCP-wrappers might serve as another example. A portmapper , commonly used by RPC-implementations, might be another? It is however correct that just a single service can be bound to a single port, but nothing keeps that service for multiplexing more services. |
Quote: |
Now the browser has a newly created socket, with a random port number of its own. Let's assume the random port number is 1500. The browser will then ask the operating system to connect that socket to socket number 80 on machine A |
output generated using printer-friendly topic mod, All times are GMT + 2 Hours