Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2013-07-19 14:40:56 →
Size: 631
Editor: AndrewStone
Comment:
← Revision 3 as of 2014-02-14 20:27:53 → ⇥
Size: 623
Editor: 192
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
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. A group is identified by a well-known [[HandleT]], 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.

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 HandleT, 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)