88 lines
3.1 KiB
C++
88 lines
3.1 KiB
C++
#ifndef FRAMEWORK_DATAPOOL_HASHKPOOLPARAMETERSIF_H_
|
|
#define FRAMEWORK_DATAPOOL_HASHKPOOLPARAMETERSIF_H_
|
|
#include <framework/datapool/PoolEntryIF.h>
|
|
#include <framework/ipc/MessageQueueSenderIF.h>
|
|
#include <framework/housekeeping/HousekeepingMessage.h>
|
|
#include <map>
|
|
|
|
class LocalDataPoolManager;
|
|
class DataSetIF;
|
|
/**
|
|
* @brief Type definition for local pool entries.
|
|
*/
|
|
using lp_id_t = uint32_t;
|
|
using LocalDataPool = std::map<lp_id_t, PoolEntryIF*>;
|
|
using LocalDataPoolMapIter = LocalDataPool::iterator;
|
|
|
|
/**
|
|
* @brief This interface is implemented by classes which posses a local
|
|
* data pool (not the managing class). It defines the relationship
|
|
* between the local data pool owner and the LocalDataPoolManager.
|
|
* @details
|
|
* Any class implementing this interface shall also have a LocalDataPoolManager
|
|
* member class which contains the actual pool data structure
|
|
* and exposes the public interface for it.
|
|
* This is required because the pool entries are templates, which makes
|
|
* specifying an interface rather difficult. The local data pool can be
|
|
* accessed by using the LocalPoolVariable, LocalPoolVector or LocalDataSet
|
|
* classes.
|
|
*
|
|
* Architectural Note:
|
|
* This could be circumvented by using a wrapper/accessor function or
|
|
* implementing the templated function in this interface..
|
|
* The first solution sounds better than the second but
|
|
* the LocalPoolVariable classes are templates as well, so this just shifts
|
|
* the problem somewhere else. Interfaces are nice, but the most
|
|
* pragmatic solution I found was to offer the client the full interface
|
|
* of the LocalDataPoolManager.
|
|
*/
|
|
class HasLocalDataPoolIF {
|
|
public:
|
|
virtual~ HasLocalDataPoolIF() {};
|
|
|
|
static constexpr uint8_t INTERFACE_ID = CLASS_ID::LOCAL_POOL_OWNER_IF;
|
|
static constexpr lp_id_t NO_POOL_ID = 0xffffffff;
|
|
|
|
virtual object_id_t getObjectId() const = 0;
|
|
|
|
/** Command queue for housekeeping messages. */
|
|
virtual MessageQueueId_t getCommandQueue() const = 0;
|
|
|
|
/** Is used by pool owner to initialize the pool map once */
|
|
virtual ReturnValue_t initializePoolEntries(
|
|
LocalDataPool& localDataPoolMap) = 0;
|
|
|
|
/** Can be used to get a handle to the local data pool manager. */
|
|
virtual LocalDataPoolManager* getHkManagerHandle() = 0;
|
|
|
|
/**
|
|
* Returns the minimum sampling frequency, which will usually be the
|
|
* period the pool owner performs its periodic operation-
|
|
* @return
|
|
*/
|
|
virtual dur_millis_t getPeriodicOperationFrequency() const = 0;
|
|
|
|
/**
|
|
* This function is used by the pool manager to get a valid dataset
|
|
* from a SID
|
|
* @param sid Corresponding structure ID
|
|
* @return
|
|
*/
|
|
virtual DataSetIF* getDataSetHandle(sid_t sid) = 0;
|
|
|
|
/* These function can be implemented by pool owner, as they are required
|
|
* by the housekeeping message interface */
|
|
virtual ReturnValue_t addDataSet(sid_t sid) {
|
|
return HasReturnvaluesIF::RETURN_FAILED;
|
|
};
|
|
virtual ReturnValue_t removeDataSet(sid_t sid) {
|
|
return HasReturnvaluesIF::RETURN_FAILED;
|
|
};
|
|
virtual ReturnValue_t changeCollectionInterval(sid_t sid,
|
|
dur_seconds_t newInterval) {
|
|
return HasReturnvaluesIF::RETURN_FAILED;
|
|
};
|
|
};
|
|
|
|
#endif /* FRAMEWORK_DATAPOOL_HASHKPOOLPARAMETERSIF_H_ */
|