Project
Loading...
Searching...
No Matches
o2::framework::DataSender Class Reference

Allow injecting policies on send. More...

#include <DataSender.h>

Public Member Functions

 DataSender (ServiceRegistryRef registry)
 
void send (fair::mq::Parts &, ChannelIndex index)
 
std::unique_ptr< fair::mq::Message > create (RouteIndex index)
 
void reset ()
 
void verifyMissingSporadic () const
 

Detailed Description

Allow injecting policies on send.

Definition at line 33 of file DataSender.h.

Constructor & Destructor Documentation

◆ DataSender()

o2::framework::DataSender::DataSender ( ServiceRegistryRef  registry)

Fill the mPresents with the outputs which are not timeframes.

Check if all the inputs are of kind Timeframe / Optional and that the completion policy is the default one. If not, we actually reset the mPresentDefaults to be empty, so that the check is disabled.

Definition at line 48 of file DataSender.cxx.

Member Function Documentation

◆ create()

std::unique_ptr< fair::mq::Message > o2::framework::DataSender::create ( RouteIndex  index)

Definition at line 95 of file DataSender.cxx.

◆ reset()

void o2::framework::DataSender::reset ( )

Reset the datasender to a clean state so that we can track what whill be sent in the next iteration and eventually complain if one of the Lifetime::Timeframe is not create / sent.

Definition at line 113 of file DataSender.cxx.

◆ send()

void o2::framework::DataSender::send ( fair::mq::Parts &  parts,
ChannelIndex  index 
)

Definition at line 101 of file DataSender.cxx.

◆ verifyMissingSporadic()

void o2::framework::DataSender::verifyMissingSporadic ( ) const

Actually verify if all the selected outputs have been sent. Notice how I think there are a few cases in which we might have a false positive, since I one could have a completion policy which creates two required messages in two different iterations.

Definition at line 118 of file DataSender.cxx.


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