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

[Kevin Klues]

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

Modified Files:
	tep108.html 
Log Message:
minor updates to TEP108 before finalization



Index: tep108.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep108.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep108.html	5 Jan 2007 18:53:43 -0000	1.7
--- tep108.html	10 Jan 2007 08:46:52 -0000	1.8
***************
*** 312,318 ****
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">28-Mar-2005</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.6</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-12-12</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
--- 312,318 ----
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">28-Mar-2005</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.7</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-01-05</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
***************
*** 503,525 ****
  }
  </pre>
- <p>The diagram below shows how a simple shared resource can be
- built from a dedicated resource by using the Resource interface
- provided by an arbiter:</p>
- <pre class="literal-block">
-          /|\                    /|\
-           |                      |
-           | Data Interface       | Resource
-           |                      |
- --------------------------------------------
- |               Shared Resource            |
- --------------------------------------------
-          /|\                    /|\
-           |                      |
-           | Data Interface       | Resource
-           |                      |
- ----------------------      -----------
- | Dedicated Resource |      | Arbiter |
- ----------------------      -----------
- </pre>
  <p>A client lets an arbiter know it needs access to a resource by
  making a call to request(). If the resource is free,
--- 503,506 ----
***************
*** 549,552 ****
--- 530,552 ----
  are not able to use it.  If a call to isOwner fails, then no call
  should be made to commands provided by that resource.</p>
+ <p>The diagram below shows how a simple shared resource can be
+ built from a dedicated resource by using just the Resource interface
+ provided by an arbiter.:</p>
+ <pre class="literal-block">
+          /|\                    /|\
+           |                      |
+           | Data Interface       | Resource
+           |                      |
+ --------------------------------------------
+ |               Shared Resource            |
+ --------------------------------------------
+          /|\                    /|\
+           |                      |
+           | Data Interface       | Resource
+           |                      |
+ ----------------------      ----------------
+ | Dedicated Resource |      |    Arbiter   |
+ ----------------------      ----------------
+ </pre>
  <p>An arbiter MUST provide exactly one parameterized Resource interface,
  where the parameter is a client ID, following the Service
***************
*** 578,586 ****
  </pre>
  <p>In contrast to the parameterized Resource interface provided by an arbiter,
! only a single ArbiterInfo interface is provided. †Its purpose is
  to allow one to find out:</p>
  <ul class="simple">
  <li>Whether the resource for which it is arbitrating use is currently in use or not</li>
! <li>Which client is using it. †</li>
  </ul>
  <p>One can view ArbiterInfo as an interface for obtaining global information about
--- 578,586 ----
  </pre>
  <p>In contrast to the parameterized Resource interface provided by an arbiter,
! only a single ArbiterInfo interface is provided.  Its purpose is
  to allow one to find out:</p>
  <ul class="simple">
  <li>Whether the resource for which it is arbitrating use is currently in use or not</li>
! <li>Which client is using it.</li>
  </ul>
  <p>One can view ArbiterInfo as an interface for obtaining global information about
***************
*** 908,921 ****
  respective arbitration components that have been built using them are
  given below:</p>
! <blockquote>
! <p>Queuing Policies:
! - FcfsResourceQueueC
! - RoundRobinResourceQueueC</p>
! <p>Arbiters:
! - SimpleFcfsArbiterC
! - FcfsArbiterC
! - SimpleRoundRobinArbiterC
! - RoundRobinArbiterC</p>
! </blockquote>
  <p>Keep in mind that neither the implementation of an arbiter nor its
  queuing policy can be used to explicitly restrict access to an
--- 908,923 ----
  respective arbitration components that have been built using them are
  given below:</p>
! <p>Queuing Policies:</p>
! <ul class="simple">
! <li>FcfsResourceQueueC</li>
! <li>RoundRobinResourceQueueC</li>
! </ul>
! <p>Arbiters:</p>
! <ul class="simple">
! <li>SimpleFcfsArbiterC</li>
! <li>FcfsArbiterC</li>
! <li>SimpleRoundRobinArbiterC</li>
! <li>RoundRobinArbiterC</li>
! </ul>
  <p>Keep in mind that neither the implementation of an arbiter nor its
  queuing policy can be used to explicitly restrict access to an