Farid Hajji <[EMAIL PROTECTED]> writes: > > > Network-wide unique identifiers like task-IDs, ports, etc... are a nice > > > thing to have. One idea may be to organize all nodes of a collective > > > in a distributed kind of (hurdisch) filesystem. IDs would then be > > > simple paths and could be located with some kind of distributed > > > lookup() functionality: > > > > It was always my plan to have a single IP address for a collective. > > (The collective might use IP for communication between its component > > systems, but those addresses would be entirely internal.) > > You certainly want to assign a multicast IP address to the collective, > right?
No, that's not necesary. At least in IPv4, multicast is too uncertain to rely on. But there are other tricks that can work. :) _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
