hmbdc
simplify-high-performance-messaging-programming
Public Member Functions | List of all members
hmbdc::app::MessageHead Class Reference

#include <Message.hpp>

Inheritance diagram for hmbdc::app::MessageHead:
hmbdc::app::MessageWrap< Message > hmbdc::app::MessageWrap< app::InBandHasMemoryAttachment< tips::domain_detail::ipc_from< JustBytes > > > hmbdc::app::MessageWrap< app::InBandHasMemoryAttachment< tips::domain_detail::ipc_from< Message > > > hmbdc::app::MessageWrap< InBandHasMemoryAttachment< JustBytes > > hmbdc::app::MessageWrap< InBandHasMemoryAttachment< Message > > hmbdc::app::MessageWrap< JustBytes > hmbdc::app::MessageWrap< tips::domain_detail::ipc_from< JustBytes > > hmbdc::app::MessageWrap< tips::domain_detail::ipc_from< Message > > hmbdc::app::MessageWrap< hmbdc::app::hasMemoryAttachment > hmbdc::app::MessageWrap< hmbdc::tips::tcpcast::SessionDropped > hmbdc::app::MessageWrap< hmbdc::tips::tcpcast::SessionStarted > hmbdc::app::MessageWrap< SessionDropped > hmbdc::app::MessageWrap< SessionStarted >

Public Member Functions

 __attribute__ ((packed)) desc
 not usable when inbandUnderlyingTypeTag is used
 

Detailed Description

It is recommneded that a Message type do not have significant dtor defined because the message could travel through process bundaries or through network


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