Changes between Version 8 and Version 9 of FeddMulti


Ignore:
Timestamp:
Sep 20, 2011 11:49:50 AM (8 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddMulti

    v8 v9  
    1414
    1515One aspect of combining multiple environments is building a single overall topology, even if no individual player will be able to see all of it.  We use a simple label-matching constraint resolver to combine topology fragments.  Each node in a fragment may be annotated with constraints that describe how it can be attached to nodes in other fragments.  Each node has one or more attachment points, each of which as one or more labels attached to it, called the attachment point's type.  Additionally each attachment point may only be attached to points that have labels specified in its "Link to" list.
     16
     17The labels on each attachment point are just labels that the designer chooses.  They shape the composition based on the matching constraints on other attachnemt points.
    1618
    1719In the example below, the two left most nodes have a single attachment point of type "Single".  They can only be attached to points of type "Node".  The next node has connections of type "Node" that can connect to either "Node" or "Single" connections.  They combine to form a 3-node fragment with one attachment point type "Node" that can connect to either "Node" or "Single" connections.
     
    9294}}}
    9395
     96In ns-2 the constraints are encoded as comments as an expedient.  DETER and fedd are moving away from the programmatic topology expression, and the relative difficulties of encoding such constranints in ns-2/tcl vs. XML is an example of why.  The overhead of adding new ns-2/tcl is much higher than parsing a few new XML elements.
     97
    9498== Composing Fragments ==
    9599