[Tinyos-devel] message_t thoughts: encapsulations and interfaces

[Miklos Maroti]

Hi Eric,

> So I would propose we split things up into two parts.
> 1) Writing encapsulations.
> needed for AM: dest(16), src(16), len (8), group(8), and type(8)
> ie.  simple AMencap(dest,  type) which would default to compiled in static
> definitions for the other values or more complete AMencap_full(dest, src,
> len, group, type).
> 2) Handing the packet off to a different layer...
> send?   send(msg).

I agree that we need to split things up, and it is not practical do
all processing by adding/removing header fields without subsequent
access to those by some interface.

For example, the AMPacket.setXXX commands are used in the following components:

apps\BaseStation\BaseStationP.nc
apps\tutorials\RssiDemo\InterceptBase\BaseStationP.nc
tos\lib\net\6lowpan\IPP.nc
tos\lib\net\lqi\LqiRoutingEngineP.nc
tos\lib\net\tymo\LoopBackM.nc
tos\lib\net\tymo\mh\MHEngineM.nc
tos\system\AMQueueEntryP.nc

I have to point out that PacketAcknowledgement also have to access the
IEEE 802.15.4 header fields, so that should also be either passed down
with send() or set separately with an interface. I am not even trying
to search for all users of the PacketAcknowledgement interface.

Miklos