All Classes and Interfaces
Class
Description
A
ComponentId consists of two parts: a globally unique context
(roughly - the domain where the ComponentId is valid)
and an id within the context.Some fixed, marker,
ComponentIdsWrapper to check that an iterator is used inside its originating transaction.
A transaction journal.
Types of Journal entry.
Generate a transaction quorum for a transaction as it begins
Helper class for the manage the persistent state of a transactional.
StateManagement for a number of long values, a common need
(might as well store ints as long on disk
for small numbers of integers)
StateManagement for a number of long values,
state accessed by index.
State for one detached components.
A transaction as the composition of actions on components.
Framework for implementing a
Transactional via TransactionalSystem.Interface that for components of a transaction system.
A transaction component that does nothing - can be used as a helper for
management tasks hooked into the transaction component lifecycle but which
are not stateful across restarts.
Implementation of the component interface for
TransactionalComponent.Base for transaction components that are added by external sub-systems.
Base implementation of the component interface for
TransactionalComponent.Helper operations for creating a
Transactional.Interface for the Transactional transitions.
Implementation side of a
Transactional.Control interface for a transactional system.
Wrapper for
TransactionalOne
TransactionCoordinator per group of TransactionalComponents.A view that provides information about a transaction
Call backs for the transaction lifecycle.
A transaction component with an integer supporting MR+SW (=one writer AND many readers).
Logging for transaction steps.
This class is stateless in the transaction but it records counts of
every
TransactionalComponent operations.TxnId is a identifier for a transaction.Factory for some forms of
TxnId.Generator of
TxnIds.Simple TxnId, mainly for debugging.
The states of the transaction lifecycle