• FrontPage

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.

• Programming Style Requirements

  • This chapter describes programming style so that SAFplus provides a consistent look.

Fundamental Objects

• Handle

  • This is a cluster-wide identifier

  • GlobalHandleT

    • Derives from HandleT, adds a cluster identifier to become globally unique

• Transaction

  • Cross object, node, cluster, transaction

• Checkpoint (AKA Dictionary, map, or hash table)

  • Replicated, nested, persistent, notifiable, shared memory, transactional Hash Table

  • ResourceAssociatedKeyDictionary

    • This Dictionary associates a ClusterUniqueId to each key and calls a cleanup whenever the resource represented by the ClusterUniqueId disappears (due to a fault).

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