Differences between revisions 6 and 11 (spanning 5 versions)
Revision 6 as of 2013-07-06 04:04:23
Size: 993
Editor: AndrewStone
Comment:
Revision 11 as of 2013-07-18 17:43:08
Size: 1345
Editor: AndrewStone
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
* [[General Design Requirements]]
This chapter describes general design requirements and rules-of-thumb to ensure a consistent semantic and API style across all services.
Line 13: Line 15:
  Replicated, nested, notifiable, shared memory, transactional Hash Table   Replicated, nested, persistent, notifiable, shared memory, transactional Hash Table
Line 15: Line 17:
  This [[Dictionary]] associates a ClusterUniqueId to each key and calls a cleanup whenever the resource represented by the ClusterUniqueId disappears (from a fault).   This [[Dictionary]] associates a ClusterUniqueId to each key and calls a cleanup whenever the resource represented by the ClusterUniqueId disappears (due to a fault).
Line 27: Line 29:
 * [[Fault]]
 All entities report errors to this centralized fault manager. Only it chooses to fault an resource identified by ClusterUniqueId
Line 30: Line 34:

FrontPage/TestNesting

SAFplus 7 Design Specification

* General Design Requirements This chapter describes general design requirements and rules-of-thumb to ensure a consistent semantic and API style across all services.

Fundamental Objects

Services

  • Logging Interface with SAFplus 6.x logging implementation underneath

  • Messaging Interface with SAFplus 6.x IOC messaging implementation underneath, but takes a ClusterUniqueId as a destination

  • Group Group membership and master election

  • Name String name to arbitrary data (generally a ClusterUniqueId)

  • Fault All entities report errors to this centralized fault manager. Only it chooses to fault an resource identified by ClusterUniqueId

FrontPage/TestNesting

OldFrontPage

SAFplus: FrontPage (last edited 2016-04-12 00:45:34 by AndrewStone)