#include <anna/core/Singleton.hpp>
#include <anna/core/util/Millisecond.hpp>
+#include <anna/core/mt/Mutex.hpp>
// Standard
#include <string>
+#include <vector>
#include <map>
// Local
typedef std::map <int, _concept_identification_t>::const_iterator _concept_identification_map_iter;
typedef std::map <int, _concept_identification_t>::iterator _concept_identification_map_nc_iter;
+typedef std::vector <Accumulator*> _accumulator_vector_t;
+typedef std::vector <Accumulator*>::const_iterator _accumulator_vector_it;
/**
public:
+ /** Destructor */
+ ~Engine();
+
// Sets
/**
*/
bool enabled(void) const throw() { return (a_enabled); }
+ /**
+ * There is an advantage creating Accumulators over the engine: the #asXML method will show all the controlled information
+ * easily. Anyway, you could allocate this class objects without using this. Then, this is a helper to create accumulators
+ * and centralize their reports.
+ *
+ * @return New allocated accumulator, to be used by the client
+ */
+ Accumulator *createAccumulator() throw();
/**
* Class string representation
Engine(); // private constructor
_concept_identification_map_t a_concept_identification_map;
+ _accumulator_vector_t a_accumulators; // you could create accumulators regardless the engine, but this is easier and asXML will show all the information easily
bool a_enabled;
int a_sequence_concept_id;
+ anna::Mutex a_mutex; // for logSample
bool logSample(const int & conceptId, const anna::Millisecond & unixTimestamp, const double & value) const throw();