Make NetworkConnectors two-sided

• Key: AMQ-1388
• Type: Improvement
• Status: Resolved
• Resolution: Duplicate
• Priority: Major
• Assignee: Rob Davies
• Reporter: Ron Pressler
• Fix Version/s: 5.0.0

Description

Consider the following scenario:

Several machines communicate using topics, using a hub-and-spoke topography, but instead of having all messages go through a central broker, each machine has an embedded vm broker to enable efficient intra-machine communication.
This is a common architecture.
Currently, to support such an architecture, if we want to allow dynamic addition of machines, we need to configure both a network connector on each machine to connect to the central hub, a tcp transport connector on the hub (to allow remote connections), as well as a multicast discovery on the central hub and a tcp connector on each machine to allow the hub to connect back to it.
This is redundant, because the network connector from the vm broker to the central hub should suffice to deliver messages in both directions, thus also making the discovery unnecessary and the connections easier to maintain and monitor.