File: Overlay/YMMOG/OverlayYMMOG.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.
YMMOG | (no description) |
Name | Type | Description |
---|---|---|
localPort | numeric | UDP port for YMMOG messages |
debug | bool |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
to_udp | output | gate to the UDP layer |
from_app | input | gate from the application |
to_app | output | gate to the application |
Name | Type | Description |
---|---|---|
ymmog.timeSlotSize | numeric | |
ymmog.maxPlayerLeafs | numeric | |
ymmog.treeWidth | numeric | |
ymmog.logLevel | numeric | |
ymmog.maxFailed | numeric | |
ymmog.maxFailedPings | numeric | |
ymmog.subscriptionRange | numeric | |
ymmog.unsubscriptionRange | numeric | |
ymmog.localPort | numeric | UDP port for YMMOG messages |
module OverlayYMMOG parameters: localPort: numeric, // UDP port for YMMOG messages debug: bool; gates: in: from_udp; // gate from the UDP layer out: to_udp; // gate to the UDP layer in: from_app; // gate from the application out: to_app; // gate to the application submodules: ymmog: YMMOG; parameters: debug = debug; display: "p=68,68;i=block/circle"; connections nocheck: from_udp --> ymmog.from_udp++; to_udp <-- ymmog.to_udp++; from_app --> ymmog.from_app; to_app <-- ymmog.to_app; endmodule