| CacheOptimizedData |
Historical data that implements this class can be optimized when storing to the cache by storing structural "schema"
data separately from "valued data".
|
| CacheOptimizedSchema |
A schema for cache optimized data.
|
| DataSink |
A data sink accepts history.
|
| DataSinkInformation |
|
| DatasourceData |
This interface represents historical data that knows how to store itself to a database connection.
|
| DataStore |
A DataStore is an intermediate data sink - ie, the "store" part of
"store and forward".
|
| DataStoreStatus |
|
| DataTransaction |
A data transaction is simply a group of historical data that should be stored together at the same time.
|
| ForwardTransaction |
Represents a set of historical data that shares the same schema, and thus can
likely be stored inside of a transaction in order to increase efficiency.
|
| GroupableData |
GroupableData is data that can be merged together in order to be stored more efficiently down the chain.
|
| HistoricalData |
Marker interface indicating this object is intended to be stored historically.
|
| HistoricalDataList |
|
| HistoricalTagValue |
This interface defines a piece of history coming from a tag, and is used by the history storage system.
|
| HistoryEvaluator |
Created by colby.clegg on 7/17/2015.
|
| HistoryFlavorCodec |
A HistoryFlavorCodec knows how to encode and decode a certain history flavor in binary and potentially
several text formats.
|
| HistoryManager |
This is the system that handles the store and forward system, allowing historical data to be stored in a reliable
way.
|
| HistoryStorer |
Defines a unit that can accept historical data.
|
| QuarantinedDataInfo |
|
| QuarantineManager |
|
| QuarantineStore |
This interface is used in conjunction with HistoryStorer & DataStore to indicate a store that can accept data that
should be immediately quarantined.
|
| RetryHistoricalData |
|
| ScanclassHistorySet |
|
| StoreAndForwardEngine |
|
| TransactionSet |
|