Message-ID: <520939724.183.1369151608378.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_182_1136317785.1369151608377" ------=_Part_182_1136317785.1369151608377 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
ActiveCluster provides two different abstractions which can be used inde= pendently or seamlessly together.
ActiveCluster maintains a list of Node objects, each Node representing a member =
of the Cl=
A node can optionally have some local state which is replicated to other me= mbers of the cluster.
You can look at the node list whenever you like and listen to nodes join= ing, leaving and updating their state.
In addition the Cluster (the group of nodes) and each Node in the cluster have a Destination. The other part of t= he ActiveCluster API is a simplified facade to messaging - way simpler and = more abstract than JMS - which allows you to send application level message= s to the cluster as a whole or to individual members of the cluster.
Its very easy to implement ActiveCluster on top of any messaging or netw= orking technology. The default implementation out of the box uses JMS. This= means we can take advantage of
e.g. some nodes in the cluster may not respond to application level mess= ages - they may wish to just view the cluster to monitor the full cluster b= ehaviour. Other nodes may wish to be participants but only see their immedi= ate buddy-group.
We can create sophisticated slicing & dicing of the cluster, partici= pants, state replication and application message flow using standard JMS te= chniques
For a more detailed look at the ActiveCluster, check out the javadocs------=_Part_182_1136317785.1369151608377--