Differences between revisions 1 and 2
Revision 1 as of 2013-07-18 19:30:11
Size: 619
Editor: AndrewStone
Comment:
Revision 2 as of 2013-07-19 14:40:56
Size: 631
Editor: AndrewStone
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
A group can be named via the [[Name]] service.
The Group service interacts with the messaging service, allowing several modes:
 * broadcast messages to all members of the group
 * send to master
 * local round robin
 1. A group can be named via the [[Name]] service.
 1. The Group service interacts with the messaging service, allowing several modes:
  * broadcast messages to all members of the group
  * send to master
  * local round robin
Line 13: Line 13:
The default mode is defined by the group.  The default mode is defined by the group.

The Group service consists of a client library and and active-standby server process running on the system controller nodes.

A group is identified by a well-known ClusterUniqueId, or a dynamically created one. A group can be named via the Name service and all APIs that require a group will also accept a string name.

Synergy

  1. A group can be named via the Name service.

  2. The Group service interacts with the messaging service, allowing several modes:
    • broadcast messages to all members of the group
    • send to master
    • local round robin
    The default mode is defined by the group.

SAFplus: Group (last edited 2014-07-25 21:54:45 by AndrewStone)