Re: [Embedlets-dev] Re: JAPL part of specification

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

> > 'm thinking that they shouldn't have *any* relationship besides one
being able
> > to talk to the other. The idea being the separation of the two different
APIs
> > and their respective domains...
>
> Exactly my thinking.  Which leads to the need for a "mediation" layer,
like
> the JAPL Wrapper class that I have proposed as a "best practice"
programming
> paradigm when using both Embedlets and JAPL together.  It allows for clean
> separation of the two layers.

Yes... agreed... this is what piccadilly is sopposed to be... or at least
its the first attempt, and will likley find problems in both api's ;)

[...]

> It would be based on the XML Config files and maybe properties at runtime.
I
> don't want to put much if any dynamic config information into the runtime
> system since that will be a strain on less capable platforms.  Many
Embedlet
> containers will be "pre-compiled" with their components to fit on smaller
> platforms like TINI or uVM.  Don't count on having a runtime dynamic
> interface for wiring.  Not a big deal since the wiring tool is a "build
time"
> activity and would have access to the config information (out of the XML
> files) in other ways.

Oh, I don't think you need too much in the way of "dynamic" configuration...
the way I've been working it, you would have to know what drivers you where
going to load... so the outpost contain could report that fairly easily to a
client app. once the client knows what the container has, it can control the
methods etc of the drivers... however this all implementation dependant, and
every one of us could come up with an implementation. In fact, I'd go so far
as to say that you don't even really need the JAPL to do this... but japl
being what I've been working on, of course I'm going to try and integreate
them ;)

> > my JAPL to Outpost implementation is "Piccadilly" (some of you
> > might understand the reference) and that is what I'm trying to do with
it.
>
> I'm feeling dense....what is the reference to?

heh... I though the americans among us wouldn't get it, but the Ausies and
Canucks would!

It actually a place name for an area of London (eng.). You will find people
calling places Piccadilly in a lot of english literature,... also a lot of
families with English roots might name places Piccadilly (my onw family does
that at our cottage up on Lake Joseph, and N. Ontario).
Anyway, it reffers to a place "where things come togher" a cross-roads etc.
I thought it apt because I'm trying to bring Outpost and JAPL together ;)

> > I think I'm just missing how the IO in the embedlet world is done... I
> > haven't had a lot of time lately, but am still plugging away....
>
> IO to peripherals would be through the JAPL API's (and using JAPL Wrappers
> where needed for async/interrupt driven stuff).  Other IO would be done
> through Container Services (events, logging, persistence, etc.) or through
> appropriate Adapters that link to the outside world.

I think my answer to all this is the wrappers... I'll take a look and see
what I can come up with... though I might not get to it again until next
weekend, and my week days tend to end late.

- Brill Pappin