Re: [Embedlets-dev] Device polling

[Brill P. <bri...@ro...>]

> In this way the system can be built up from mix-and-match components that
> may come from different vendors and no one component has disproportionate
> 'control'.
>
> This also gives you the flexibility to have local independent loops that
run
> at different rates if that is a requirement. You (the Embedlet user) gets
to
> determine who is in control! You (the Embedlet designer) do no have to
> accommodate multiple, mutually exclusive requirements.

Control is good... but there are situations (a lot of them) where you really
don't want users to be able to mess with the internals... I guess the
embedlet user does need to be able to take some control, but I think it
should be limited to what the environment deems "safe" or efficient... for
instance, if the embedlet container wants to poll temperature every 500uS,
the JAPL implementer is not going to allow the container to force me to make
a call to actually read the temperature that often (depending on the
granularity and speed of the sensors etc.) because it takes up resources I
need for other functions, and that I don't really want to give up to the
embedlet container.

So, I guess my point is that though you can delegate some control to the
embedlets, in a lot of circumstances, the underlying JAPL impl. *must* keep
control over itself, and prevent the embedlet(s) for putting it into an
unstable or inoperative state.

- Brill Pappin