|
Size: 1387
Comment:
|
Size: 1338
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| === General Design Requirements]] === |
* [[General Design Requirements]] |
| Line 6: | Line 5: |
| [[General Design Requirements]] |
|
| Line 11: | Line 8: |
| * ClusterUniqueId | * [[HandleT]] |
| Line 13: | Line 10: |
| * GloballyUniqueId Derives from ClusterUniqueId, adds a cluster identifier to become globally unique |
* [[GlobalHandleT]] Derives from [[HandleT]], adds a cluster identifier to become globally unique |
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
- This is a cluster-wide identifier
Derives from HandleT, adds a cluster identifier to become globally unique
- Cross object, node, cluster, transaction
- 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