One-type-per-message works best with MIG. >From past experience, I avoid "avoid overloading" unless it offers a significant advantage.
Of course you're free to encode/marshall any way you want :) On Sun, May 25, 2008 at 3:30 PM, Nicola Wegner <[EMAIL PROTECTED]> wrote: > Hi, > > I have a question about common practice in using the AM Type. > > I want to define a protocol with different types of packets. > > Should I use one AM Type for the whole protocol and distinguish between the > different kind of packets by using a custom "subtype" field at the beginning > of every payload struct? > > Or should I use a different AM Type for every packet type? When so, is there > a different way of sending packets with different AM Types beside using > multiple instances of AMSend? > > > And a question about the Tutorial "Mote-mote radio communication": > In the receive event the length of the payload is checked but not the AM > Type. Is there a specific reason for this practice? > > Thanks in advance for your help > > Nicola > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
