Approaches of interprocess communication

Damjan gdamjan at gmail.com
Sat Feb 17 15:31:07 EST 2007


> | > If a programmer decides on behalf of the user that "localhost" should
> | > be treated specially, that programmer is making an error.
> |
> | Inter-process TCP/IP communication between two processes on the same
> | host invariably uses the loopback interface (network 127.0.0.0).
> | According to standards, all addresses in that network space refer to the
> | local host, though 127.0.0.1 is conventionally used.
> |
> | The transmit driver for the loopback interface receives a datagram from
> | the local network layer and immediately announces its reception back to
> | the local network layer.
> 
> Are you saying, in that first paragraph, that if for example I telnet to
> my local host's external IP address, to a service that bound explicitly to
> the external interface -- I'll actually be going through the loopback
> interface anyway, invariably regardless of host network implementation?

On linux at least, this is true, yes.


-- 
damjan



More information about the Python-list mailing list