At 08:41 AM 1/12/99 , Ka-Ping Yee wrote:
>When a binding address is not specified, the socket listens on the given
>port number on all interfaces, producing the effect you observed.
>If you only need to bind to all interfaces or one interface, then you
>should be able to get by without extra threads.
[#] This is wonderful!
Just to double check, you're saying it is part of TCP/IP's semantics that one can use a single socket / a single port number to listen for connections coming in for this port number paired with each of the host's IP addresses, as the java.net API would seem to imply. If this isn't quite right, or isn't supported on a platform that matters, please speak up, as I'm about to proceed depending on this property. Thanks.
Using this property, it's much easier for E to deal with multiple interfaces. One listen socket per vat, period.