> My recommendation is that Teds idea of JAPL actually needs to be broken
> into 2 layes, APT, JAPL where the APT layer is a completely abstract
> interface of Abstract peripherals implemented by the platform and
> created by the APT peripheral factory, ie the APT is a wrapper for the
> proprietry libries into a common abstract peripheral toolkit.
But it already works that way! see: org.japl.peripheral
> JAPL then is a shared device driver library that is built ontop of the
> APT and so now the JAPL library is platform independent so all japl
> devices can run on any platform that supports the APT framework.
>
> I think the embedlet container implementation should provide an APT
> PeripherFactory which is used by embedlets when creating JAPL components
> which are implemented by APT components.
I don't think you need to integrate the two... embedlet access to the JAPL
is done through the Outpost implementation, and leaves it flexible... now
that implementation can have references to both... which is kind of the plan
anyway.
- Brill Pappin
|