hmbdc
simplify-high-performance-messaging-programming
|
Public Member Functions | |
void | invokedCb (size_t) HMBDC_RESTRICT 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... | |
bool | droppedCb () override |
callback called after the Client is safely taken out of the Context More... | |
![]() | |
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 void | messageDispatchingStartedCb (size_t const *pClientDispatchingStarted) |
called before any messages got dispatched - only once More... | |
virtual void | stoppedCb (std::exception const &e) |
callback called when this Client is taken out of message dispatching More... | |
virtual | ~Client () |
trivial | |
void | stopped (std::exception const &e) noexcept |
the following are for internal use, don't change or override | |
Additional Inherited Members | |
![]() | |
void | batchDone () |
the derived user's Client has the option to stop the current batch of event dispatching. More... | |
|
inlineoverridevirtual |
callback called after the Client is safely taken out of the Context
exception thrown here is ignored and return true is assumed
Reimplemented from hmbdc::app::Client< SendTransportEngine >.
|
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
dispatched | the number of messages dispatched since last invokedCb called |
Reimplemented from hmbdc::app::Client< SendTransportEngine >.