(no description)
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram. Click here to see the full picture.
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram. Click here to see the full picture.
Name | Direction | Size | Description |
---|---|---|---|
udpIn | input |
gate from the UDP layer |
|
from_lowerTier | input |
gate from the lower tier |
|
from_upperTier | input |
gate from the upper tier |
|
tcpIn | input |
gate from the TCP layer |
|
tcpOut | output |
gate to the TCP layer |
|
udpOut | output |
gate to the UDP layer |
|
to_lowerTier | output |
gate to the lower tier |
|
to_upperTier | output |
gate to the upper tier |
Name | Type | Default value | Description |
---|---|---|---|
landmark.rpcUdpTimeout | double |
default timeout value for direct RPCs |
|
landmark.rpcKeyTimeout | double |
default timeout value for routed RPCs |
|
landmark.optimizeTimeouts | bool |
calculate timeouts from measured RTTs and network coordinates |
|
landmark.rpcExponentialBackoff | bool |
if true, doubles the timeout for every retransmission |
|
landmark.debugOutput | bool |
enable debug output |
module LandmarkModules like ITier { gates: input udpIn; // gate from the UDP layer input from_lowerTier; // gate from the lower tier input from_upperTier; // gate from the upper tier input tcpIn; // gate from the TCP layer output tcpOut; // gate to the TCP layer output udpOut; // gate to the UDP layer output to_lowerTier; // gate to the lower tier output to_upperTier; // gate to the upper tier submodules: landmark: Landmark { parameters: @display("p=60,60;i=block/circle"); } connections allowunconnected: // connect our gates with the inner module udpIn --> landmark.udpIn; udpOut <-- landmark.udpOut; //appIn --> landmark.appIn; //appOut <-- landmark.appOut; }