> The embedlet/JAPL timing specifications will need to be carefully
considered
> in any mix-and-match design. If one embedlet is demanding resources or
> performance beyond those available the system is likely to fail at some
> point regardless of whether a particular JAPL or embedlet manages all of
its
> internal timing needs.
From my point of view, the JAPL impl should know about what it can, and
can't do, and be able to tell the embedlet to piss-off if its abusing the
peripheral in some way. It might also simply block the call (which will be
happening anyway in a threaded environment) or what ever other method is
relevant in the context of the peripheral.
I see this as essential to ensuring the processor is stable, regardless of
what some fool (no accusations) does to the embedlet configuration... from
the user perspective, the embedlet "server" is just a black box, they
wouldn't have a clue about the consequences of a particular configuration,
nor should they have to be concerned that they would take down the server
with their own bad/incorrect code.
- Brill Pappin
|