> > It can be a problem even within a single application. If your application > > inadvertently uses the AM IDs of things like Collection or Dissemination, > > you'd probably get some interesting results. Well, doubly-wiring a Receive > > interface would probably be caught by the compiler, but still. > > Michiel
> We probably don't want port number allocation authority because we are > only talking about net2 protocols. I am thinking a README in > tos/lib/net that lists the protocols and the AM IDs they use, if the > AM ID is not specified by the user of the protocol, should be good > enough for now. Does that work for you Michiel? Oh, I intended my comment only as "I could see this potentially being a problem", not "this is an actual problem" :) The compiler will generate a warning if you wire another receiver to an AM ID, and between CTP and dissemination, the AM types are both well known and well out of the way if you start at zero for your application AM IDs. Still, a list would be handy and > a README in tos/lib/net does sound like an excellent place for it. Kind regards, Michiel
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
