[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep118.txt,1.7,1.8

[Omprakash Gnawali]

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

Modified Files:
	tep118.txt 
Log Message:
minor edit

Index: tep118.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep118.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep118.txt	14 Jun 2007 18:26:03 -0000	1.7
--- tep118.txt	24 Aug 2007 16:29:35 -0000	1.8
***************
*** 33,38 ****
  ====================================================================
  
! Dissemination is a basic sensor network protocol. The ability to
! reliably deliver a piece of data to every node allows administrators
  to reconfigure, query, and reprogram a network.  Reliability is
  important because it makes the operation robust to temporary
--- 33,38 ----
  ====================================================================
  
! Dissemination is a a sensor network protocol that reliably delivers a
! piece of data to every node in the network. Dissemination can be used
  to reconfigure, query, and reprogram a network.  Reliability is
  important because it makes the operation robust to temporary
***************
*** 61,65 ****
  rejoins the network it will only see the most recent. The rest of this
  document describes a set of components and interfaces for a
! dissemination service of this kind.
  
  2. Dissemination interfaces
--- 61,65 ----
  rejoins the network it will only see the most recent. The rest of this
  document describes a set of components and interfaces for a
! dissemination service included in TinyOS 2.0.
  
  2. Dissemination interfaces
***************
*** 139,150 ****
  ====================================================================
  
! One issue that comes up when using this interfaces is the selection of
! a key for each value. On one hand, using unique() is easy, but this
  means that the keyspaces for two different compilations of the same
  program might be different and there's no way to support a network
! with more than one binary. On the other, having a component declare
! its own key internally means that you can run into key collisions that
! can't be resolved. In the middle, an application can select keys on
! behalf of other components.
  
  Ordinarily, dissemination keys can be generated by unique or selected
--- 139,150 ----
  ====================================================================
  
! One issue that comes up when using these interfaces is the selection
! of a key for each value. On one hand, using unique() is easy, but this
  means that the keyspaces for two different compilations of the same
  program might be different and there's no way to support a network
! with more than one binary. On the other hand, having a component
! declare its own key internally means that you can run into key
! collisions that can't be resolved. In the middle, an application can
! select keys on behalf of other components.
  
  Ordinarily, dissemination keys can be generated by unique or selected