Dataflow Runtime API
2.7.4.0
|
Classes that implement this interface provide a generic mechanism to exchange data with a remoting peer. More...
#include <Imt.Base.BSP.Simulator/Remoting/ProtocolReceiverIfc.h>
Public Member Functions | |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverIdentifyProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver)=0 |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverIdentifyResponseProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver) |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverValueGetProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver)=0 |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverValueGetResponseProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver)=0 |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverValueSetProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver)=0 |
virtual void | onDataReceived (imt::base::bsp::simulator::protocols::SimDriverValueSetResponseProtocol &protocol, const imt::base::bsp::type::DriverType::Id driverType, const uint16_t indexModule, const uint16_t indexDriver)=0 |
Classes that implement this interface provide a generic mechanism to exchange data with a remoting peer.
Each RemoteObjectIfc 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.