File: Applications/Scribe/Scribe.ned
(no description)
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.
Scribe | (no description) |
Name | Type | Description |
---|---|---|
debugOutput | bool | if debug output should be enabled |
childTimeout | numeric | seconds until a node assumes that a particular child has failed |
parentTimeout | numeric | seconds until a node assumes that a particular parent has failed |
Name | Direction | Description |
---|---|---|
from_udp | input | |
from_lowerTier | input | |
from_upperTier | input | |
to_udp | output | |
to_lowerTier | output | |
to_upperTier | output |
Name | Type | Description |
---|
module MulticastScribe parameters: debugOutput: bool, // if debug output should be enabled childTimeout: numeric, //seconds until a node assumes that a particular child has failed parentTimeout: numeric; //seconds until a node assumes that a particular parent has failed gates: in: from_udp, from_lowerTier, from_upperTier; out: to_udp, to_lowerTier, to_upperTier; submodules: scribe: Scribe; parameters: debugOutput = debugOutput, childTimeout = childTimeout, parentTimeout = parentTimeout; connections nocheck: from_lowerTier --> scribe.from_lowerTier; to_lowerTier <-- scribe.to_lowerTier; from_upperTier --> scribe.from_upperTier; to_upperTier <-- scribe.to_upperTier; from_udp --> scribe.from_udp; to_udp <-- scribe.to_udp; endmodule