[Shox-cvs] SF.net SVN: shox:[2090] trunk/conf/examples/layer-prog-Intro.txt

[<dir...@us...>]

Revision: 2090
          http://shox.svn.sourceforge.net/shox/?rev=2090&view=rev
Author:   dirk_held
Date:     2009-07-02 14:51:40 +0000 (Thu, 02 Jul 2009)

Log Message:
-----------
typos.

Modified Paths:
--------------
    trunk/conf/examples/layer-prog-Intro.txt

Modified: trunk/conf/examples/layer-prog-Intro.txt
===================================================================
--- trunk/conf/examples/layer-prog-Intro.txt	2009-07-02 14:39:00 UTC (rev 2089)
+++ trunk/conf/examples/layer-prog-Intro.txt	2009-07-02 14:51:40 UTC (rev 2090)
@@ -30,21 +30,21 @@
 returns the global pseudo random number generator, which yields random numbers with the next*()
 calls. To resolve the neighborhood directly, without having to detect them first, using extra packets,
 use the node.getNeighbors(), getNeighborCount(), or resolveNeighbor() methods. Although there are
-other public methods, which deal with neighbors, they are only used internally. Although it may be
-useful, to directly access the MAC-Layer of of a neighbors node, to check, if a packet has reached
-this node, to have exact statistics, lots of nasty things can be done this way. It is up to you, how
-you use so-called god-knowledge or god-methods, since in reality one node cannot directly access
-other nodes inner state.
+other public methods, which deal with neighbors, they are only used internally. 
+Although it may be useful, to directly access the MAC-Layer of of a neighbors node, to check, if a 
+packet has reached this node, to have exact statistics, lots of nasty things can be done this way. 
+It is up to you, how you use so-called god-knowledge or god-methods, since in reality one node 
+cannot directly access other nodes inner state.
 
 2. The packet-class
 
-Each packet has its own header, a current direction (up or down the layer-stack), a timestamp
-of the creation time and a pointer to the inner packet of the next higher layer. The creating layer
-uses the Packet(Address sender, NodeId receiver) constructor to create the innermost layer,
-where the header is actually the payload of the packet. Use NodeId.ALLNODES as broadcast-
-address, if needed. The other two constructors are used down the layer-stack, to wrap the 
-layer-specific header around a packet, which was received from a higher layer. Only the network-
-layer may specify a new receiver, which is the next hop along the path to the final receiver. 
+Each packet has its own header, a current direction (up or down the layer-stack), a timestamp of the 
+creation time and a pointer to the inner packet of the next higher layer. The creating layer uses the 
+Packet(Address sender, NodeId receiver) constructor to create the innermost layer, where the header is 
+actually the payload of the packet. Use NodeId.ALLNODES as broadcast-address, if needed. The other two 
+constructors are used down the layer-stack, to wrap the layer-specific header around a packet, which 
+was received from a higher layer. Only the network-layer may specify a new receiver, which is the next 
+hop along the path to the final receiver. 
 
 here is an extract of the methods of the packet class:
 
@@ -134,7 +134,7 @@
 MAC-Layer. The layerState of the application-layer is used to form a return code. The enum
 ApplicationState offers the values CREATED, WAITING, RUNNING, FAILED, DONE. If the value is 
 not set to DONE before the end, the value is set to FAILED. At the end, the number of done and
-failed nodes is printed. Thus this just for your quick information at the end.
+failed nodes is printed. This just for your quick information at the end.
 
 9. dumping link- and node-states
 
@@ -144,5 +144,5 @@
 stored as link- or node-state. See OSRL at lines ~60-97 for some wrapper routines, which can write 
 a link- or node-state. After completing a run, start the GUI and open the file  history.compact
 in the shox directory with the "File/Open Log File ..." menu. After parsing the data, a new tab
-"Monitor" should become visible. The menu "Mapping/Config Mapping ..." offers the possibility, to
+"Monitor" should be created. The menu "Mapping/Config Mapping ..." offers the possibility, to
 assign certain values to certain visualizations, like node color, node/link-label. 


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.