[Tinyos-2-commits] CVS: tinyos-2.x/doc/html/tutorial lesson8.html, 1.4, 1.5

[Kevin Klues]

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

Modified Files:
	lesson8.html 
Log Message:
Update of files to align them with TEP108 changes to ResourceController interface to rename it to ResourceDefaultOwner.  TEP103 hasn't been altered, and we still need to decide what should be done with it exactly.

Index: lesson8.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tutorial/lesson8.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** lesson8.html	12 Dec 2006 18:22:53 -0000	1.4
--- lesson8.html	4 Feb 2007 19:54:42 -0000	1.5
***************
*** 80,84 ****
  
  <p>
! Shared resources are essentially built on top of dedicated resources, with access to them being controlled by an arbiter component.  In this way, <b>power managers</b> can be used to automatically control the power state of these resources through their <tt>AsyncStdControl</tt>, <tt>StdControl</tt>, or <tt>SplitControl</tt> interfaces.  They communicate with the arbiter (through the use of a <tt>ResourceController</tt> interface), monitoring whether the resource is being used by any of its clients and powering it on/off accordingly.  The figure below shows how an arbiter component and a power manager can be wired together to provide arbitration and automatic power management for a shared resource.
  </p>
  
--- 80,84 ----
  
  <p>
! Shared resources are essentially built on top of dedicated resources, with access to them being controlled by an arbiter component.  In this way, <b>power managers</b> can be used to automatically control the power state of these resources through their <tt>AsyncStdControl</tt>, <tt>StdControl</tt>, or <tt>SplitControl</tt> interfaces.  They communicate with the arbiter (through the use of a <tt>ResourceDefaultOwner</tt> interface), monitoring whether the resource is being used by any of its clients and powering it on/off accordingly.  The figure below shows how an arbiter component and a power manager can be wired together to provide arbitration and automatic power management for a shared resource.
  </p>
  
***************
*** 93,97 ****
  
  <p>
! The arbiter component provides the <tt>Resource</tt>, <tt>ArbiterInfo</tt>, <tt>ResourceRequested</tt>, and <tt>ResourceController</tt> interfaces and uses the <tt>ResourceConfigure</tt> interface.  The power manager doesn't provide any interfaces, but uses one of either the <tt>AsyncStdControl</tt>, <tt>StdControl</tt>, or <tt>SplitControl</tt> interfaces from the underlying resource, as well as the <tt>ResourceController</tt> interface provided by the arbiter.  The figure below shows how these interface are then wired together with the implementation of a shared resource.  Please refer to TEP 108 for more information on arbiters and TEP 115 for more information on Power Managers.
  </p>
  
--- 93,97 ----
  
  <p>
! The arbiter component provides the <tt>Resource</tt>, <tt>ArbiterInfo</tt>, <tt>ResourceRequested</tt>, and <tt>ResourceDefaultOwner</tt> interfaces and uses the <tt>ResourceConfigure</tt> interface.  The power manager doesn't provide any interfaces, but uses one of either the <tt>AsyncStdControl</tt>, <tt>StdControl</tt>, or <tt>SplitControl</tt> interfaces from the underlying resource, as well as the <tt>ResourceDefaultOwner</tt> interface provided by the arbiter.  The figure below shows how these interface are then wired together with the implementation of a shared resource.  Please refer to TEP 108 for more information on arbiters and TEP 115 for more information on Power Managers.
  </p>
  
***************
*** 308,312 ****
    ResourceConfigure = Arbiter;
    SharedResourceImplP.ArbiterInfo -> Arbiter;
!   PowerManager.ResourceController -> Arbiter;
    
    PowerManager.SplitControl -> ResourceP;
--- 308,312 ----
    ResourceConfigure = Arbiter;
    SharedResourceImplP.ArbiterInfo -> Arbiter;
!   PowerManager.ResourceDefaultOwner -> Arbiter;
    
    PowerManager.SplitControl -> ResourceP;