The Serializable interface provides the API used to serialize headers, control messages and events. More...
#include <serializable.h>
Public Member Functions | |
| virtual | ~Serializable () |
| virtual Serialization | serialize () const |
Protected Member Functions | |
| Serializable ()=default | |
Detailed Description
The Serializable interface provides the API used to serialize headers, control messages and events.
Definition at line 50 of file serializable.h.
Constructor & Destructor Documentation
◆ ~Serializable()
|
inlinevirtual |
Definition at line 53 of file serializable.h.
◆ Serializable()
|
protecteddefault |
Member Function Documentation
◆ serialize()
|
inlinevirtual |
Gets the serialized form of the object
- Returns
- serialization
- Exceptions
-
SerializationException
- Note
- Most objects use Google Protocol Buffers to perform serialization. This is why the Serialization type is a std::string. The serialized data is binary, non-printable data. The std::string just provides a simple API.
- https://developers.google.com/protocol-buffers/
Reimplemented in EMANE::Controls::R2RISelfMetricControlMessage, EMANE::Controls::R2RINeighborMetricControlMessage, EMANE::Controls::OTATransmitterControlMessage, EMANE::Controls::R2RIQueueMetricControlMessage, EMANE::Controls::FlowControlControlMessage, EMANE::Events::CommEffectEvent, EMANE::Events::AntennaProfileEvent, EMANE::Events::FadingSelectionEvent, EMANE::Events::LocationEvent, EMANE::Events::PathlossEvent, EMANE::Models::IEEE80211ABG::MACHeaderMessage, EMANE::Models::TDMA::BaseModelMessage, EMANE::Models::TimingAnalysis::ShimHeaderMessage, EMANE::Messages::LoggerRecordMessage, EMANE::Models::RFPipe::MACHeaderMessage, EMANE::Models::IEEE80211ABG::OneHopNeighborsEvent, and EMANE::Models::CommEffect::ShimHeader.
Definition at line 69 of file serializable.h.
The documentation for this class was generated from the following file:
