Implementing the possibility to built a raw DataPacket representation with freely selectable content.

TESTING

Check doxygen, because several methods have changed!

Up to now only representation of float is possible. Should be enhanced to be a template also being able to deal with double.

File raw_mem3.h

Up to now only representation of float is possible. Should be enhanced to be a template also being able to deal with double.

File ss_meta_info.h

Rename file to TiA_meta_information

Class tia::Channel

Write (or rename to) more appropriate method-names(e.g. id_--> name_)

Class tia::ControlConnection

Improve documentation of this class.

Class tia::ControlMsgDecoder

Check constructor

Find out what decodeMsg() is exactly planned/used for

Class tia::ControlMsgEncoderXML

Find out what "decodeHeader" is exactly planned/used for.

Global tia::DataPacket3Impl::DataPacket3Impl (const DataPacket3Impl &src)

Check for memory leaks! (can occur, if raw_mem objects are built)

Global tia::DataPacket3Impl::getRaw ()

Inserting data after building a raw representation, won't change the raw memory and will deliver a pointer pointing to "the old" DataPacket.

Global tia::DataPacket3Impl::getRequiredRawMemorySize (void *mem, boost::uint32_t bytes_available)

Rewrite this mehtod as its size is now available inside the data packet.

Global tia::DataPacket3Impl::insertDataBlock (std::vector< double > v, boost::uint32_t signal_flag, boost::uint16_t blocks, bool prepend=false)

If needed: Implementing the possibility to store the same signal type comming from different devices.

Global tia::DataPacket3Impl::reset (void *mem)

Implementing safety checks, as far as possible.

Size field is skipped!

Global tia::DataPacket3Impl::~DataPacket3Impl ()

Check for memory leaks! (can occur, if raw_mem objects are built)

Class tia::DataPacketImpl

Implementing the possibility to built a raw DataPacket representation with freely selectable content.

Global tia::DataPacketImpl::DataPacketImpl (const DataPacketImpl &src)

Check for memory leaks! (can occur, if raw_mem objects are built)

Global tia::DataPacketImpl::getRaw ()

Inserting data after building a raw representation, won't change the raw memory and will deliver a pointer pointing to "the old" DataPacket.

Global tia::DataPacketImpl::insertDataBlock (std::vector< double > v, boost::uint32_t signal_flag, boost::uint16_t blocks, bool prepend=false)

If needed: Implementing the possibility to store the same signal type comming from different devices.

Global tia::DataPacketImpl::reset (void *mem)

Implementing safety checks, as far as possible.

Size field is skipped!

Global tia::DataPacketImpl::~DataPacketImpl ()

Check for memory leaks! (can occur, if raw_mem objects are built)

Global tia::RawMem3::RawMem3 (boost::uint8_t packet_version, boost::uint32_t flags, boost::uint64_t packet_id, boost::uint64_t packet_nr,::uint64_t timestamp,::vector< boost::uint16_t > &nr_channels, std::vector< boost::uint16_t > &samples_per_channel, std::vector< double > &data)

Refactor doxygen

Class tia::Signal

Find a way to be consistent with signal types and signal type names within TiA.

Class tia::SSConfig

Rename class to TiAConfig

Class tia::SubjectInfo

Adjust class to use enums properly (e.g. sex).

Check if mandatory settings are done (now done in XML parser).

Class tia::TCPConnection

Class tia::TiAServer

Implement mechanisms to detect "impossible" configurations.

Define "invisible magic constants" like fs = 0 for aperiodic devices.

Implement mechanisms to ensure that aperiodics are used correctly (e.g. blocksize)

Global tia::TiAServer::initialize (std::map< std::string, std::string > &subject_info, std::map< std::string, std::string > &server_settings)

Check if wrong configuration is checked within this code.

Is it a good idea to use maps for configuration (especially server config)?

Class tia::UDPDataServer

Maybe use transmission into multiple subnets or use multicast.