[Tinyos-beta-commits] CVS: tinyos-1.x/beta/teps/txt tep108.txt, 1.2, 1.3

[David Gay]

Update of /cvsroot/tinyos/tinyos-1.x/beta/teps/txt
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv15472

Modified Files:
	tep108.txt 
Log Message:
don't use "standard"


Index: tep108.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-1.x/beta/teps/txt/tep108.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** tep108.txt	31 Mar 2005 01:03:14 -0000	1.2
--- tep108.txt	31 Mar 2005 22:02:42 -0000	1.3
***************
*** 55,61 ****
    clear documentation of which requests could happen simultaneously.
  
! In light of all these problems, TinyOS 2.x introduces standard resource
! reservation mechanisms for use by components providing access to shared
! resources.
  
  2. Resource sharing in TinyOS 2.x
--- 55,60 ----
    clear documentation of which requests could happen simultaneously.
  
! In light of all these problems, TinyOS 2.x introduces resource reservation
! mechanisms for use by components providing access to shared resources.
  
  2. Resource sharing in TinyOS 2.x
***************
*** 75,81 ****
  
  - Resource reservation: the service must be reserved before use, via the
! standard Resource interface. This approach is described in Section 3.
! Because many services will have similar approaches to resource sharing
! (e.g., round-robin, or priority-based), TinyOS includes standard arbiters
  implementing various resource sharing policies. These arbiters are
  described in Section 4.
--- 74,80 ----
  
  - Resource reservation: the service must be reserved before use, via the
! Resource interface. This approach is described in Section 3.  Because many
! services will have similar approaches to resource sharing (e.g.,
! round-robin, or priority-based), TinyOS includes default arbiters
  implementing various resource sharing policies. These arbiters are
  described in Section 4.
***************
*** 168,172 ****
  reservation is purely a reservation of the software component itself.
  
! 4. Standard arbiters
  ====================================================================
  
--- 167,171 ----
  reservation is purely a reservation of the software component itself.
  
! 4. Default arbiters
  ====================================================================
  
***************
*** 174,178 ****
  interface, but this would be a waste of programmer effort and would lead to
  inconsistent resource sharing policies across services. Instead, TinyOS
! includes a number of standard resource arbiters, in the form of generic
  components, which implement the Resource interface. All of these arbiters
  also provide a ResourceUser interface which can be interrogated to find the
--- 173,177 ----
  interface, but this would be a waste of programmer effort and would lead to
  inconsistent resource sharing policies across services. Instead, TinyOS
! includes a number of default resource arbiters, in the form of generic
  components, which implement the Resource interface. All of these arbiters
  also provide a ResourceUser interface which can be interrogated to find the
***************
*** 197,202 ****
  resource allocation in the style of TinyOS 1.x.
  
! The StandardArbiter provides round-robin arbitration:
! generic component StandardArbiter {
    provides interface Resource[uin8_t id];
    provides interface ResourceUser;
--- 196,201 ----
  resource allocation in the style of TinyOS 1.x.
  
! The RoundRobinArbiter provides round-robin arbitration:
! generic component RoundRobinArbiter {
    provides interface Resource[uin8_t id];
    provides interface ResourceUser;