Simple Module Vast

File: Overlay/Vast/Vast.ned

C++ definition: click here

(no description)

Usage diagram:

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.

Used in compound modules:

If a module type shows up more than once, that means it has been defined in more than one NED file.

OverlayVast

Implementation of the Vast overlay as described in "Scalable peer-to-peer networked virtual environment" by S.-Y. Hu and G.-M. Liao, published in NetGames �04: Proceedings of 3rd ACM SIGCOMM workshop on Network and system support for games, pages

Parameters:

Name Type Description
localPort numeric

UDP port for Vast messages

debugOutput bool

enable debug output

keyLength numeric

overlay key length in bits

measureNetwInitPhase bool

gather statistics when bootstrapping

useCommonAPIforward bool

enable CommonAPI forward() calls

drawOverlayTopology bool

draw arrow to successor node?

hopCountMax numeric

maximum number of overlay hops

joinOnApplicationRequest bool

only join the overlay on application request

lookupParallelPaths numeric

number of parallel paths

lookupParallelRpcs numeric

number of nodes to ask in parallel

lookupSecure bool

true, if all nodes should be identified with a ping

lookupMerge bool

true, if parallel Rpc results should be merged

lookupFailedNodeRpcs bool

communicate failed nodes

lookupRedundantNodes numeric

number of next hops in each step

useNextHopRpc bool

use RPCs for route messages

useBaseLookup bool

use the base lookup class

iterativeLookup bool

do iterative instead of recursive lookups

collectPerHopDelay bool

delay statistics for single hops

debugVastOutput bool
ignoreFalseKeys bool
AOIWidth numeric
joinTimeout numeric
pingTimeout numeric

Gates:

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

rpc_in input

gate for RPC sendDirect

Source code:

simple Vast
    parameters:
        localPort: numeric,    // UDP port for Vast messages
        debugOutput: bool,    // enable debug output
        keyLength : numeric,    // overlay key length in bits
        measureNetwInitPhase: bool,    // gather statistics when bootstrapping
        useCommonAPIforward : bool,      // enable CommonAPI forward() calls
        drawOverlayTopology : bool,    // draw arrow to successor node?
        hopCountMax : numeric,    // maximum number of overlay hops
        joinOnApplicationRequest : bool,    // only join the overlay on application request

        lookupParallelPaths : numeric,    // number of parallel paths
        lookupParallelRpcs : numeric,    // number of nodes to ask in parallel
        lookupSecure : bool,    // true, if all nodes should be identified with a ping
        lookupMerge : bool,    // true, if parallel Rpc results should be merged
        lookupFailedNodeRpcs : bool,    // communicate failed nodes
        lookupRedundantNodes : numeric,    // number of next hops in each step
        useNextHopRpc : bool,            // use RPCs for route messages

        useBaseLookup : bool,    // use the base lookup class
        iterativeLookup : bool,    // do iterative instead of recursive lookups
        collectPerHopDelay : bool,    // delay statistics for single hops

        debugVastOutput: bool,
        ignoreFalseKeys: bool,
        AOIWidth: numeric,
        joinTimeout: numeric,
        pingTimeout: numeric;

    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
        in: rpc_in;    // gate for RPC sendDirect
endsimple