rti::sub::cond::DataReaderStatusConditionHandler< T > Class Template Reference

<<interface>> Realization of a functor handler that handles the status of a dds::sub::DataReader. More...

#include <DataReaderStatusConditionHandler.hpp>

Public Member Functions
	DataReaderStatusConditionHandler (dds::sub::DataReader< T > &reader, dds::sub::DataReaderListener< T > *listener, const dds::core::status::StatusMask &listener_mask)
	Creates a new rti::core::sub::DataReaderStatusConditionHandler instance.

Detailed Description

template<typename T>
class rti::sub::cond::DataReaderStatusConditionHandler< T >

<<interface>> Realization of a functor handler that handles the status of a dds::sub::DataReader.

A rti::core::sub::DataReaderStatusConditionHandler demultiplexes a dds::sub::DataReader status change into the corresponding callback of a provided dds::sub::DataReaderListener implementation.

Note that the dds::sub::DataReaderListener notifications have different considerations than if the were made by the dds::sub::DataReader directly:

• Context: The dds::sub::DataReaderListener callback context is the one of the thread that dispatches the dds::core::cond::Condition where this handler is set. For instance, if you attach the condition to a rti::core::cond::AsyncWaitSet, the context will be one of the threads within the pool.
• Status clearing: All the dds::sub::DataReader's enabled statuses are cleared upon condition dispatch except the dds::core::status::StatusMask::data_available(), which will not be cleared until your application reads the data.
• Exclusive Area: Restrictions depend on the context of the dipsatching thread. For instance, if the rti::core::cond::AsyncWaitSet dispatches the condition, the listener notications are free of any exclusive area restrictions.

The rti::core::sub::DataReaderStatusConditionHandler is a convenience to handle the status changes of a dds::sub::DataReader. You can install a rti::core::sub::DataReaderStatusConditionHandler as the handler of a reader's dds::core::cond::StatusCondition. You can then attach it to a dds::core::cond::WaitSet or rti::core::cond::AsyncWaitSet and receive status changes notifications through a specific dds::sub::DataReaderListener implementation instance.

Constructor & Destructor Documentation

template<typename T >

rti::sub::cond::DataReaderStatusConditionHandler< T >::DataReaderStatusConditionHandler ( dds::sub::DataReader< T > &  reader, dds::sub::DataReaderListener< T > *  listener, const dds::core::status::StatusMask &  listener_mask  )

inline

Creates a new rti::core::sub::DataReaderStatusConditionHandler instance.

The created DataReaderStatusConditionHandler can set as functor handler in any dds::core::cond::Condition and will demultiplex the specified status changes from the specified dds::sub::DataReader

Parameters

reader	<<in>> The dds::sub::DataReader for which the status changes are demultiplexed to the specified listener
listener	<<in>> that receives the status changes notifications from the specified reader.
listener_mask	<<in>> Specifies which status changes from the reader to demultiplex to the listener.

Returns

A new instance or NULL on error.

See Also

dds::sub::DataReader

dds::sub::DataReader::listener(Listener* the_listener,const dds::core::status::StatusMask& event_mask)

dds::core::cond::StatusCondition

functor handler