[ https://jira.jboss.org/jira/browse/JGRP-910?page=com.atlassian.jira.plugi... ] Bela Ban commented on JGRP-910: ------------------------------- Possible solution: --> The 'members' variable remains in TP, but is only used when the transport is non-shared --> When we need to send a message to all members *without* multicasting, the following happens: - Regular transport: - We iterate over 'members' and send the same message to every member (same as now) - Shared transport - TP.ProtocolAdapter adds the cluster name to the message as a header - We grab the header and retrieve the cluster name - We look up the corresponding TP.ProtocolAdapter in up_prots - TP.ProtocolAdapter also maintains a 'members' membership variable. We use it to iterate over the members -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-910?page=com.atlassian.jira.plugi... ] Bela Ban commented on JGRP-910: ------------------------------- We'll leave 'members' in TP: when a non-singleton, we add the current view, when using a shared transport, we add *all* members of all views to it (union). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira