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

[Phil Levis]

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

Modified Files:
	tep116.txt 
Log Message:
Incorporate more comments.


Index: tep116.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep116.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep116.txt	14 Mar 2007 01:50:40 -0000	1.7
--- tep116.txt	14 Mar 2007 01:56:33 -0000	1.8
***************
*** 139,143 ****
  it is a way for queues and other packet buffering components
  to store the full state of a packet without requiring additional
! memory allocation.
  
  The distinction between ``payloadLength`` and ``maxPayloadLength``
--- 139,143 ----
  it is a way for queues and other packet buffering components
  to store the full state of a packet without requiring additional
! memory allocation. 
  
  The distinction between ``payloadLength`` and ``maxPayloadLength``
***************
*** 233,236 ****
--- 233,242 ----
  type. It also provides commands to set these fields, for the same
  reason that Packet allows a caller to set the payload length.
+ Packet interfaces SHOULD provide accessors
+ and mutators for all of their fields to enable queues and other
+ buffering to store values in a packet buffer. Typically, a component
+ stores these values in the packet buffer itself (where the field is),
+ but when necessary it may use the metadata region of message_t or other
+ locations.
  
  2.2 Sending interfaces