hmbdc
simplify-high-performance-messaging-programming
Public Member Functions | List of all members
hmbdc::app::utils::pingpong_detail::Pinger< Sender > Struct Template Reference
Inheritance diagram for hmbdc::app::utils::pingpong_detail::Pinger< Sender >:
hmbdc::app::Client< Pinger< Sender >, Ball > hmbdc::app::MessageHandler< Pinger< Sender >, Messages ... >

Public Member Functions

void messageDispatchingStartedCb (uint16_t threadSerialNumber) override
 called before any messages got dispatched - only once More...
 
void stoppedCb (exception const &e) override
 callback called when this Client is taken out of message dispatching More...
 
void invokedCb (uint16_t) override
 this callback is called all the time (frequently) - the exact timing is after a batch of messages are dispatched. After this call returns, the previously dispatched message's addresses are no longer valid, which means if you cache the event addresses in the previous handleMessageCb()s, you cannot use those after the return of the next invokeCb function. More...
 
- Public Member Functions inherited from hmbdc::app::Client< Pinger< Sender >, Ball >
char const * hmbdcName () const
 return the name of thread that runs this client, override if necessary More...
 
std::tuple< char const *, int > schedSpec () const
 an overrideable method. returns the schedule policy and priority, override if necessary priority is only used when policy is "SCHED_RR", or "SCHED_FIFO" More...
 
size_t maxBatchMessageCount () const
 an overridable method. client receives events in batches and the max batch size is controllable when running in direct mode Context. Here is to specify the max size. More...
 
virtual bool droppedCb ()
 callback called after the Client is safely taken out of the Context More...
 
virtual ~Client ()
 trivial
 
void stopped (std::exception const &e) noexcept
 internal use, don't change or override
 

Member Function Documentation

◆ invokedCb()

template<typename Sender>
void hmbdc::app::utils::pingpong_detail::Pinger< Sender >::invokedCb ( uint16_t  threadSerialNumber)
inlineoverridevirtual

this callback is called all the time (frequently) - the exact timing is after a batch of messages are dispatched. After this call returns, the previously dispatched message's addresses are no longer valid, which means if you cache the event addresses in the previous handleMessageCb()s, you cannot use those after the return of the next invokeCb function.

you can collectively process the messages received/cached so far here, or do something needs to be done all the time like powering another message loop

Parameters
threadSerialNumberthe number indicating which thread is in action

Reimplemented from hmbdc::app::Client< Pinger< Sender >, Ball >.

◆ messageDispatchingStartedCb()

template<typename Sender>
void hmbdc::app::utils::pingpong_detail::Pinger< Sender >::messageDispatchingStartedCb ( uint16_t  threadSerialNumber)
inlineoverridevirtual

called before any messages got dispatched - only once

this is the place some preparation code goes to

Parameters
threadSerialNumbernormally the number indicating which thread is in action, except when REGISTERED_MESSAGE_SIZE == 0 it is another undefined value

Reimplemented from hmbdc::app::Client< Pinger< Sender >, Ball >.

◆ stoppedCb()

template<typename Sender>
void hmbdc::app::utils::pingpong_detail::Pinger< Sender >::stoppedCb ( exception const &  e)
inlineoverridevirtual

callback called when this Client is taken out of message dispatching

after this call the Client is still at hook from the Context point of view (until droppedCb is called), so don't delete this Client yet or add it back to the Context. any exception thrown here is ignored,

Parameters
ethe exception that caused the Client to be taken out of message dispatching e could be thrown by the Client itself in a callback function to voluntarily take itself out

Reimplemented from hmbdc::app::Client< Pinger< Sender >, Ball >.


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