[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep119.txt,1.17,1.18

[Omprakash Gnawali]

Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv10876

Modified Files:
	tep119.txt 
Log Message:
more fixes

Index: tep119.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep119.txt,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** tep119.txt	21 Aug 2008 23:11:12 -0000	1.17
--- tep119.txt	4 Sep 2008 22:05:00 -0000	1.18
***************
*** 24,36 ****
  
  The memo documents the interfaces, components, and semantics used by
! collection protocol in TinyOS 2.x. Collection provides best-effort,
! multihop delivery of packets to one of a set of collection points.
! There may be multiple collection points in a network, and in this
! case the semantics are *anycast* delivery to at least one of the
! collection points. A node sending a packet does not specify which of
! the collection points the packet is destined to.  The union of the
! paths from each node to one or more of the collection points forms a
! set of trees, and in this document assume that collection points are
! the roots of these trees.
   
  
--- 24,36 ----
  
  The memo documents the interfaces, components, and semantics used by
! the collection protocols in TinyOS 2.x. Collection provides
! best-effort, multihop delivery of packets to one of a set of
! collection points.  There may be multiple collection points in a
! network, and in this case the semantics are *anycast* delivery to at
! least one of the collection points. A node sending a packet does not
! specify which of the collection points the packet is destined to.  The
! union of the paths from each node to one or more of the collection
! points forms a set of trees, and in this document we assume that
! collection points are the roots of these trees.
   
  
***************
*** 91,97 ****
  
  The collection infrastructure can be multiplexed among independent
! applications, by means of a collection identifier. While data traffic
! in the protocol is multiplexed through these identifiers, control
! traffic is not: all data traffic uses the same routing topology.
  
  The nodes that generate data to be sent to the root are *senders*.
--- 91,99 ----
  
  The collection infrastructure can be multiplexed among independent
! applications, by means of a collection identifier. The collection
! identifier is used to identify different data traffic at the sender,
! intermediate-nodes, or the receiver, much like port number in TCP. All
! data traffic, regardless of the collection identifier, use the same
! routing topology.
  
  The nodes that generate data to be sent to the root are *senders*.
***************
*** 131,139 ****
  Receive during instantiation.
  
! The set of all roots and the paths that
! lead to them form the collection routing infrastructure in the network.
! For any connected set of nodes implementing the collection protocol 
! there is only one collection infrastructure, *i.e.*, all roots in this 
! set active at the same time are part of the same infrastructure.
  
  The RootControl interface configures whether a node is a
--- 133,141 ----
  Receive during instantiation.
  
! The set of all roots and the paths that lead to them form the
! collection routing infrastructure in the network.  For any connected
! set of nodes implementing the collection protocol there is only one
! collection infrastructure, *i.e.*, all roots in this set active at the
! same time are part of the same infrastructure.
  
  The RootControl interface configures whether a node is a
***************
*** 176,183 ****
  
  
! CollectionC MAY have additional interfaces. These additional
! interfaces MUST have default functions on all outgoing invocations
! (commands for uses, events for provides) of those interfaces so that
! it can operate properly if they are not wired.
  
  Components SHOULD NOT wire to CollectionC.Send. The generic
--- 178,185 ----
  
  
! CollectionC MAY have additional interfaces. All outgoing invocations
! (commands for uses, events for provides) of those interfaces MUST have
! default functions. Those default functions enable CollectionC to
! operate properly even when the additional interfaces are not wired.
  
  Components SHOULD NOT wire to CollectionC.Send. The generic
***************
*** 190,194 ****
  different am_id_t values represent different protocols operating on
  top of active messages. All packets sent with a particular
! collection_id_t generally have the same payload format, so that
  snoopers, intercepters, and receivers can parse them properly.
  
--- 192,196 ----
  different am_id_t values represent different protocols operating on
  top of active messages. All packets sent with a particular
! collection_id_t generally SHOULD have the same payload format, so that
  snoopers, intercepters, and receivers can parse them properly.