File: Applications/i3/I3.ned
C++ definition: click here
Module for I3 servers
Author: Antonio Zea
The following diagram shows usage relationships between modules, networks and channels. Unresolved module (and channel) types are missing from the diagram. Click here to see the full picture.
If a module type shows up more than once, that means it has been defined in more than one NED file.
OverlayI3 | Container for I3 module and trigger table Author: Antonio Zea |
Name | Type | Description |
---|---|---|
debugOutput | bool | inherited from BaseApp |
triggerTimeToLive | numeric | expiration time for triggers |
serverPort | numeric | server port |
Name | Direction | Description |
---|---|---|
from_lowerTier | input | gate from the lower tier |
to_lowerTier | output | gate to the lower tier |
from_upperTier | input | gate from the upper tier |
to_upperTier | output | gate to the upper tier |
from_udp | input | gate from the UDP layer |
to_udp | output | gate to the UDP layer |
direct_in | input | gate for sendDirect |
simple I3 parameters: debugOutput: bool, // inherited from BaseApp triggerTimeToLive, // expiration time for triggers serverPort; // server port gates: in: from_lowerTier; // gate from the lower tier out: to_lowerTier; // gate to the lower tier in: from_upperTier; // gate from the upper tier out: to_upperTier; // gate to the upper tier in: from_udp; // gate from the UDP layer out: to_udp; // gate to the UDP layer in: direct_in; // gate for sendDirect endsimple