On Mon, 2005-11-28 at 14:01 -0500, Franc Tan wrote:
> I guess I'm not understanding how MVirus works.  I've looked at the
> latest Mate' code and I see how MHandlerStore sits on top of MVirus.
> The only hooks that I see MHandlerStore has with MVirus is the
> registerCapsule command and handling the MVirus events.  

MVirus isn't intended to be a general component that you can plug in
anywhere; it's pretty enmeshed with the rest of the VM engine.

> The problem I have is understanding how to introduce a new capsule
> that should be propogated throughout the network.  Does
> registerCapsule() command perform this duty?  

No. The way you introduce a new capsule is through the network.
Generally, you introduce it to a single node over a serial link using
the Mate' java toolchain. The network then propagates it to every node.
It turns out that, in the context of Mate', the idea of a node being
able to generate a new capsule itself is kind of dangerous, so the
software structure doesn't let you do so easily.

> I understand the part that the versions array will be initialized to
> zeros, but how do you let MVirus know that you have a new capsule that
> needs to be propogated?  How do you update the version number? 

You install a new capsule.

> What I've done so far is to take your MVirus implementation and write
> it in the latest version of TinyOS.  I would like to use your
> algorithm to efficiently brodcast data and commands to a network of
> motes.  I'm not using it in the context of Mate'.  Right now I just
> have a simple app that uses MVirus and I'm trying to use it to
> disseminate commands.  I must not be wiring up all the proper
> components to get it working correctly? 

If you want a general dissemination component, I suggest that you look
at Drip (lib/Drip). Gil put a bit of work into building a dissemination
stack where you can plug in data types (such as commands).

Phil

_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to