[ https://issues.jboss.org/browse/JGRP-2098?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2098 at 9/22/16 2:02 AM: --------------------------------------------------------- We could place {{NAMING}} over {{NAKACK2}} / {{UNICAST3}}, so we don't have to implement our own reliability. To make things simple, the name cache would be populated as follows: * The joiner sends its address-name mapping to everyone after having joined successfully * The joiner gets the full name cache from the coordintor, or - alternatively - everyone sends its name to the joiner after the new view has been installed At the time the coordinator receives the JOIN(P) request, P's logical name would not be known yet, but we could (for example) simply print the IP address:port of IpAddressUUID if the logical name is not known. After the protocol skteched out above has run, logical names would be available and used to print IpAddressUUIDs. was (Author: belaban): We could place {{NAMING}} over {{NAKACK2}} / {{UNICAST3}}, so we don't have to implement our own reliability. To make things simple, the name cache would be populated as follows: * The joiner sends its address-name mapping to everyone after having joined successfully * The joiner gets the full name cache from the coordintor, or - alternatively - everyone sends its name to the joiner after the new view has been installed -- This message was sent by Atlassian JIRA (v6.4.11#64026)