[
https://issues.jboss.org/browse/JGRP-2224?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2224:
--------------------------------
I don't like the idea of having to point to a different file, that's just another
moving part that can be missing.
I ended up picking the solution where {{MULTI_PING}} needs to be somewhere above all other
discovery protocols, e.g.
{code:xml}
<TCP ... />
<TCPPING initial_hosts="127.0.0.1[7800]" port_range="0"/>
<PING />
<MPING/>
<FILE_PING/>
<MULTI_PING async_discovery="true"/>
<MERGE3/>
...
{code}
The reason I did _not_ pick the embeded configuration above is that it would have required
an awkward match between protocol IDs and header IDs, and forwarding of messages up the
stack.
Multiple discovery protocols
----------------------------
Key: JGRP-2224
URL:
https://issues.jboss.org/browse/JGRP-2224
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0.8
Allow for multiple discovery protocols. This would allow us to use a single configuration
which includes discovery protocols for multiple cloud providers.
The discovery protocols could be queried sequentially (return on result), or in
parallel.
Investigate whether we need a super discovery protocol which instantiates the individual
protocols, or whether each protocol should be changed e.g. to forward events down the
stack.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)