RsvpHelloMsg
classRSVP HELLO REQUEST message
This class adds convenience get() and set() methods to the generated base class, but no extra data.
XXX FIXME all RSVP message have kind=RSVP_TRAFFIC to distinguish them: if they are RsvpPacket: use packet->getRsvpKind() if they are RsvpHelloMsg: only one type exists
thus, we need dynamic_cast to find out what it is that's not good. we don't use kind, because kind is used by IP QoS mechanism (use DS field for IP QoS instead???)
Inheritance diagram
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Extends
Name | Type | Description |
---|---|---|
RsvpMessage | class |
RSVP message common part |
Fields
Name | Type | Description |
---|---|---|
request | bool | |
ack | bool | |
srcInstance | int | |
dstInstance | int | |
rsvpKind | int | |
mutable | bool | |
complete | bool | |
correct | bool | |
properlyRepresented | bool | |
chunkLength | b | |
rawBin | string[] | |
rawHex | string[] | |
tags | RegionTagSet::cObjectRegionTag[] |
Source code
// // RSVP HELLO REQUEST message // // This class adds convenience get() and set() methods to the generated // base class, but no extra data. // // XXX FIXME all RSVP message have kind=RSVP_TRAFFIC // to distinguish them: // if they are RsvpPacket: use packet->getRsvpKind() // if they are RsvpHelloMsg: only one type exists // // thus, we need dynamic_cast to find out what it is // that's not good. we don't use kind, because kind // is used by IP QoS mechanism (use DS field for IP QoS instead???) // class RsvpHelloMsg extends RsvpMessage { bool request; bool ack; int srcInstance; int dstInstance; rsvpKind = HELLO_MESSAGE; }File: src/inet/networklayer/rsvpte/RsvpHelloMsg.msg