|
void | messageDispatchingStartedCb (size_t const *) override |
| called before any messages got dispatched - only once More...
|
|
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...
|
|
void | stoppedCb (std::exception const &e) override |
| should not happen ever unless an exception thrown More...
|
|
| RecvTransportImpl (Config const &cfg, OutputBuffer &outputBuffer) |
| ctor More...
|
|
void | start () |
| start the show by schedule the mesage recv
|
|
void | handleMessageCb (TypeTagBackupSource const &t) |
| only used by MH
|
|
size_t | sessionsRemainingActive () const |
| check how many other parties are sending to this engine More...
|
|
void | schedule (SysTime fireAt, Timer &timer) |
| schedule the timer to start at a specific time More...
|
|
void | cancel (Timer &timer) |
| cancel a timer previously scheduled with the TimerManager 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 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 |
| the following are for internal use, don't change or override
|
|
template<typename OutputBuffer , typename AttachmentAllocator >
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
-
dispatched | the number of messages dispatched since last invokedCb called |
Reimplemented from hmbdc::app::Client< RecvTransportEngine< OutputBuffer, AttachmentAllocator > >.