Dataflow Runtime API  2.7.4.0
Public Member Functions | List of all members
imt::base::bsp::simulator::protocols::ProtocolIfc Class Reference

Classes that implement this interface provide a generic mechanism to exchange data with a remoting peer. More...

#include <Imt.Base.BSP.Simulator/Protocols/ProtocolIfc.h>

Inheritance diagram for imt::base::bsp::simulator::protocols::ProtocolIfc:
imt::base::core::serialization::SerializableIfc imt::base::bsp::simulator::protocols::SimDriverIdentifyProtocol imt::base::bsp::simulator::protocols::SimDriverIdentifyResponseProtocol imt::base::bsp::simulator::protocols::SimDriverValueGetProtocol imt::base::bsp::simulator::protocols::SimDriverValueGetResponseProtocol imt::base::bsp::simulator::protocols::SimDriverValueSetProtocol imt::base::bsp::simulator::protocols::SimDriverValueSetResponseProtocol

Public Member Functions

uint16_t getProtocolIdentifier ()
 
void setProtocolIdentifier (uint16_t protocolIdentifier)
 
- Public Member Functions inherited from imt::base::core::serialization::SerializableIfc
virtual ~SerializableIfc (void)
 Destructor.
 
virtual void deserialize (Deserializer &deserializer)=0
 Deserialize this object from the given deserializer. More...
 
virtual void serialize (Serializer &serializer) const =0
 Serialize this object into the given serializer. More...
 

Detailed Description

Classes that implement this interface provide a generic mechanism to exchange data with a remoting peer.

Each ProtocolIfc implementation has a unique id, that is inserted in the byte stream sent to the remoting peer, that allows to identify the responsible remote object on the other side. The data send / received is handled in the serialize and deserialize methods.


The documentation for this class was generated from the following file: