[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1353) Discovery: all subclasses should only return a list of PhysicalAddresses instead of doing the sending themselves
Bela Ban (JIRA)
jira-events at lists.jboss.org
Tue Aug 16 06:13:17 EDT 2011
[ https://issues.jboss.org/browse/JGRP-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban resolved JGRP-1353.
----------------------------
Resolution: Done
> Discovery: all subclasses should only return a list of PhysicalAddresses instead of doing the sending themselves
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-1353
> URL: https://issues.jboss.org/browse/JGRP-1353
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.0
>
>
> Currently, Discovery.sendGetMembersRequest() is implemented separately in all subclasses of Discovery. However, the code in it is almost the same; we grab a list of PhysicalAddresses and send a discovery request to every element.
> This functionality should be moved into Discovery, and every subclass should only (1) return the list of PhysicalAddresses and (2) override a method getAddresses().
> Method Discovery.sendDiscoveryRequest() would then call getAddresses() and send a discovery request to every element. We also need to add a method sendDiscoveryRequestsInParallel() to Discovery, which is overridden in every subclass, and determines whether to use a separate timer thread for each discovery request, or not.
> Note that getAddresses() may set metadata, too, e.g. in TCPGOSSIP, where it fetches metadata (logical name, physical address, UUID) from the GossipRouter and sets it in its local cache
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list