File: Tier2/DHTTestApp/DHTTestApp.ned
Compound module for a simple DHT test application
Author: Bernhard Heep, Ingmar Baumgart
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.
DHTTestApp | Simple module of the DHT test application |
Name | Direction | Description |
---|---|---|
from_lowerTier | input | gate from the lower tier |
from_upperTier | input | gate from the upper tier |
from_udp | input | gate from the UDP layer |
trace_in | input | gate for trace file commands |
to_lowerTier | output | gate to the lower tier |
to_upperTier | output | gate to the upper tier |
to_udp | output | gate to the UDP layer |
Name | Type | Description |
---|---|---|
dhtTestApp.debugOutput | bool | enable debug output |
dhtTestApp.testInterval | numeric | time interval for DHT operations (put/get/modify) |
dhtTestApp.testTtl | numeric | TTL for stored test records |
dhtTestApp.activeNetwInitPhase | bool | send messages when network is in init phase? |
module DHTTestAppModules gates: in: from_lowerTier; // gate from the lower tier in: from_upperTier; // gate from the upper tier in: from_udp; // gate from the UDP layer in: trace_in; // gate for trace file commands out: to_lowerTier; // gate to the lower tier out: to_upperTier; // gate to the upper tier out: to_udp; // gate to the UDP layer submodules: dhtTestApp: DHTTestApp; display: "i=block/app"; connections nocheck: from_lowerTier --> dhtTestApp.from_lowerTier; to_lowerTier <-- dhtTestApp.to_lowerTier; trace_in --> dhtTestApp.trace_in; endmodule