Messages can be received on the input port. More...

#include <Imt.Base.Dff.ActiveParts/PortInput.h>

Inheritance diagram for imt::base::dff::activeparts::PortInput:

Public Member Functions
	PortInput (void)
	Constructor.

virtual	~PortInput (void)
	Destructor.

virtual void	receive (const uint16_t protocolIdentifier, const imt::base::core::serialization::SerializableIfc *const pEventData, const int32_t eventDataSizeBytes=imt::base::dff::runtime::EVENTDATA_SIZE_BYTES) const

virtual imt::base::dff::runtime::RuntimeCore::CoreHandle	getReceiveHandle (void) const

virtual imt::base::dff::runtime::RuntimePriority::Id	getReceivePriority (void) const

void	registerActivePart (imt::base::dff::runtime::ExecutableIfc &activePart)
	Register run method of ActivePart in RuntimeCore. More...

Public Member Functions inherited from imt::base::dff::activeparts::ReceiverIfc
virtual	~ReceiverIfc (void)
	Destructor.

Detailed Description

Messages can be received on the input port.

Each ActivePart has exactly one input port where all messages are enqueued.

Member Function Documentation

virtual imt::base::dff::runtime::RuntimeCore::CoreHandle imt::base::dff::activeparts::PortInput::getReceiveHandle ( void ) const

virtual

virtual imt::base::dff::runtime::RuntimePriority::Id imt::base::dff::activeparts::PortInput::getReceivePriority ( void ) const

virtual

virtual void imt::base::dff::activeparts::PortInput::receive	(	const uint16_t	protocolIdentifier,
		const imt::base::core::serialization::SerializableIfc *const	pEventData,
		const int32_t	eventDataSizeBytes = `imt::base::dff::runtime::EVENTDATA_SIZE_BYTES`
	)		const

virtual

void imt::base::dff::activeparts::PortInput::registerActivePart ( imt::base::dff::runtime::ExecutableIfc & activePart )