joe.polastre at gmail.com
Thu Jan 6 11:52:56 PST 2005
In theory, any request while starting will return FAIL, likewise for
stopping. Ie, you have to wait for the event to come back.
On Thu, 06 Jan 2005 12:03:54 -0800, Philip Levis <pal at eecs.berkeley.edu> wrote:
> I have some questions about SplitControl. Unfortunately, it looks like
> the file is just a copy of StdControl with some additional events
> thrown in.
> What is the proper calling convention for SplitControl? Specifically,
> if I have called start() but have not received startDone(), can I call
> stop()? Similarly, if I have called stop() but have not received a
> stopDone(), can I call start()?
> The case for init() is pretty clear: no. But for start/stop it's less
> clear. The comment on startDone() suggests that the rule is no: "Notify
> components that the component has been started and is ready to receive
> other commands." But since there's no statement about "other commands"
> in stopDone, I'm led to believe this refers to the functional
> interfaces, and not SplitControl.
> "We shall not cease from exploration
> And the end of all our exploring
> Will be to arrive where we started
> And know the place for the first time."
> - T. S. Eliot, 'Little Gidding'
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
More information about the Tinyos-devel