Package com.boylesoftware.cb2.bcmproviders.sockethub

Broadcast Messaging provider implementation, which uses a centralized network server to distribute messages.

See:
Description

Class Summary

Hub	Standalone program, which plays the role of a message hub, or server.
SocketHubBCMProvider	Implementation of BCM provider, which uses a centralized hub to broadcast messages to all registered cluster members over TCP.

Package com.boylesoftware.cb2.bcmproviders.sockethub Description

Broadcast Messaging provider implementation, which uses a centralized network server to distribute messages.

When a new cluster member is started, it connects to the server (the hub) using TCP and registers itself. Later, when it needs to broadcast a message it sends it to the hub, and the hub relays it to all registered cluster members. Using a centralized server allows having cluster members that do not know about other members - all that a cluster member needs to know to broadcast messages is where the hub is. It means that cluster members may be added or removed dynamically, which is an advantage. On the other hand, one disadvantage of this approach is that the central server is a critical point and if it goes down the BCM subsystem stops working.

To make this BCM provider implementation work you must specify the following application properties:

• com.boylesoftware.cb2.broadcastMessaging.sockethub.host - name or IP address of the host where the cetral hub is running.
• com.boylesoftware.cb2.broadcastMessaging.sockethub.port - TCP port on which the hub is listening for connections.

Also, the hub process must be running on the server. The hub is implemented by class Hub. See its comments to find out how to run the hub.