File: Applications/i3/I3BaseApp.ned
C++ definition: click here
Base module for I3 applications.
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.
Name | Type | Description |
---|---|---|
clientPort | numeric | client port |
serverPort | numeric | server port |
triggerRefreshTime | numeric | interval for trigger refreshing |
sampleRefreshTime | numeric | interfal for trigger sample refreshing |
bootstrapTime | numeric | time to wait for overlay to bootstrap |
initTime | numeric | time to wait for I3 to bootstrap |
cacheSize | numeric | size of cache of stored id/server references |
idStoreTime | numeric | expiration time of stored id/server references |
serverTimeout | numeric | time to wait before server is marked as unavailable |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
from_app | input | gate from the application |
from_overlay | input | gate from the overlay |
to_udp | output | gate to the UDP layer |
to_app | output | gate to the application |
to_overlay | output | gate to the overlay |
simple I3BaseApp parameters: clientPort, // client port serverPort, // server port triggerRefreshTime, // interval for trigger refreshing sampleRefreshTime, // interfal for trigger sample refreshing bootstrapTime, // time to wait for overlay to bootstrap initTime, // time to wait for I3 to bootstrap cacheSize, // size of cache of stored id/server references idStoreTime, // expiration time of stored id/server references serverTimeout; // time to wait before server is marked as unavailable gates: in: from_udp; // gate from the UDP layer in: from_app; // gate from the application in: from_overlay; // gate from the overlay out: to_udp; // gate to the UDP layer out: to_app; // gate to the application out: to_overlay; // gate to the overlay endsimple