Layering the predicate won't prevent the data item from being broadcasted, it will just prevent your application from seeing the change unless some condition is satisfied. In order to prevent it from rebroadcasting data, you'll need to change the logic of the specific dissemination implementation you're using.
Kaisen KURT PETERS wrote: > I've been reviewing the various sites and papers describing Trickle and > dissemination, such as: > http://docs.tinyos.net/index.php/Network_Protocols > http://docs.tinyos.net/index.php/Dissemination > http://www.tinyos.net/tinyos-2.x/doc/html/tep118.html > > ...as well as looking at code in $tosdir/tos/lib/net > One thing isn't clear to me... > > Where would be the best place to add some logic to prevent child nodes from > further forwarding messages? > > It seems that hops actually take place by signaling > "DisseminationCache.newData()", but it isn't clear where a top level program > would be able to control as stated in TEP118: > "For example, if you want have a > dissemination that causes only nodes which satisfy a predicate to > apply a change, you can do that by making the <t> a struct that stores > a predicate and data value in it, and layering the predicate > evaluation on top of the above interfaces." > > How is the predicate evaluation coded on top, as stated? Or, where is the > best module to do it? > > > Thanks, > Kurt > > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
