Re: [Embedlets-dev] Re:[HW] cvs module for JAPL

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

> > <choke>, <choke>
> > I guess that sort of defines the domains we'll be working under ;)
however I
> > don't think the package names have to be domain names in this case (see
my
> > previous post).
>
> Aside from leveraging the domain name system, how else does one assure
that
> one's packages are globally unique?  How do we know that someone in Russia
> right now is not working on a project that uses 'cork' as its top level
package
> name?

how does the fellow in Russia avoid naming conflicts with the java. package?
We're attempting to develop a standard here, that runs on embedded devices
where control over the device is important, rather than the "haphazard" way
desktop and server software is used... not only that, but Outpost is
supposed to remove the nececity of programming the chips.

My point is, I think we're safe from accidental naming conflicts, whatever
we decide to name the packages.

> > This is true, although cork will likely become part of whatever standard
the
> > JAPL becomes, because really Cork is an impl of the JAPL...
>
> But what if someone else wants to develop their own implementation of the
JAPL
> interfaces?  If JAPL were its own separate entity then it would be easier
for
> multiple implementations of JAPL to be made and other projects besides
> Embedlets would also be more likely to use them.

Oh, I don't mean add cork to the JAPL library... I'm talking about a
reference impl the same way Tomcat is a reference impl for the Servlet spec.
Still separate, but made for each other ;)

> > I was
> > thinking that along side JAPL could be put JHAL (Java Hardware
Abstraction
> > Layer) which Cork has tried to do in providing a common hardware layer
so
> > that the same code runs on a JStamp, uVM or a TINI.
>
> This is an interesting idea and I am going to need do some thinking on
it...

Yah, it's a "fuzzy" area where the JAPL is concerned, because the processor
itself could be considdered a "Peripheral" that can be controlled and
configured in its own right.
Originally cork was supposed to abstract the devices (what the JAPL will do)
but the second implemntation has tried to abstract not only the devices, but
the runtime environment, so that I can write a "cork" app, and drop it into
a TINI or a JStamp, and it works the first time.

> In the mean time, I just checked at godaddy.com and jhal.org is available
for
> $8.95/year if you are interested. ;-)

Na, already got a domain I never use ;)

> > a place to drop documents would be good ;)
>
> Hmmm.  As a developer I think you are able to create folders in the CVS?
> Anyway, I added a 'japl' directory inside of the dev_docs directory so go
ahead
> and start placing your materials here.

Don't know, didn't try, I thought it should be "cleared" with the project
manager first, in case you had some special configuration you wanted to
implement.

- Brill Pappin