>[1] Loopback inet IPC is actually a fairly useful beast since it allows > cooperating applications to rendezvous without requiring a writable > fileystem.
Much of our stack uses loopback RPC and this works fine; loopback inet is more difficult to use, particularly because it requires a well-known port. I would love to see an example of current use of AF_INET loopback as an IPC mechanism. Note also that we try to make sure that non of the internal IPC mechanisms don't listen to the world; AF_INET isn't the easiest way to achieve that) Note that the current RFE 6434380 was initially filed for both network and IPC; but since there are so many way to construct local IPC, e.g., using a mmap'ed queue, there seems to be no easy way to enforce this. Casper
