SAFplus 7 Design Specification
- 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
- This is a cluster-wide identifier
Derives from HandleT, adds a cluster identifier to become globally unique
- Cross object, node, cluster, transaction
Checkpoint (AKA Dictionary, map, or hash table)
- Replicated, nested, persistent, notifiable, shared memory, transactional Hash Table
This Dictionary associates a Handle to each key and calls a cleanup whenever the resource represented by the Handle disappears (due to a fault).
- A group of threads that are applied to a list of tasks.
- This class intermediates between the messaging layer (send/receive) and the application code. It manages messaging buffers and optimizes frequency of message sending verses message size.
Services
Logging Applications and other services can log to shared memory. A log server will "scrape" the shared memory and post the message to log channels and/or files.
Messaging Interface with SAFplus 6.x IOC messaging implementation underneath, but takes a Handle as a destination
Group Group membership and cluster master election
Name String name to arbitrary data (generally a Handle)
Fault All entities report errors to this centralized fault manager. Only it chooses to fault a resource (node or process).
Availability Management Core process that starts and monitors applications
Remote Procedure Call Fast and efficient RPC subsystem