Brill suggests:
> Now the question as I see it, is how much do we try and make the two
> dependant from one another... if they are, we will loose flexibility and
> the ability for developers to use the japl without Outpost, however if
> they are not we will expand the size of our code to some degree (or so I
> would assume).
I think they should be decoupled as much as is humanly possible. Tight
coupling in that area would be disastrous from a flexibility and maintenance
perspective.
A developer should be able to use Outpost/Embedlets with or without JAPL.
Similarily, JAPL should not depend on Embedlets. The one is a container
architecture, the other is a hardware abstraction layer. They need to be
distinct.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
