RE: [Embedlets-dev] RE: MediaController

[Christopher S. <cs...@oo...>]

Ted,

MediaController is definitely a JAPL interface that surfaces inter-processor
communication. I think that it should be available to the Embedlet
components directly.

Where you divide things up from there is not as important. It would, I
think, be OK for one JAPL to use another but what you give up is the
flexibility to plug and play, dynamically configure and 'soft-wire' that is
supported by Embedlets.

My feeling is that JAPL's main mission should be to establish a common
ground for the emerging Java board and chip makers to publish their I/O
libraries without the encumbrance of the Embedlet infrastructure. Higher
level functionality such as a motor controller would seem to fit the
Embedlet model a little more closely because of the 'soft-wire' event model,
configuration and services that are available. If you start to build these
into JAPL then the complexity and weight will deter acceptance.

That being said, there is nothing to prevent one from publishing a complex
control component under JAPL, then providing an Embedlet wrapper to drop it
into an Embedlet container.

Time will tell where the most effective deployment strategy lies.

For the time being let's get the interface out there and see how it fits. I
have built the network package for the Embedlets side and will publish it
over the weekend. If you want me to put the MediaController together, I will
do that as well.

Chris

> _______________________________________________
>
> Chris wrote:
>
> >If we all agree on the MediaController interface then everyone can
> >implement their favorite hardware device in their xxxMediaController
> >and expect a plug and play deployment. This could be the first
> >operational JAPL! Lets go!
>
> Chris, this is a killer idea!  The first question I have is whether the
> MediaController is a JAPL interface or an Embedlet Adapter?  In
> my mind, JAPL
> interfaces were designed to represent I/O circuits like a servo
> controller, a
> temperature sensor, an emergency stop button, etc.
>
> For example, I want the CNC controller Embedlet that I am
> building to use a
> something like a JAPL ServoController interface to control the
> movements of the
> XYZ positioning system.  I want to be able to have the Embedlet
> send a message
> like:
>
> servoController.moveTo(X, Y, Z, Speed);
>
> to the servo mechanism and I don't want to know how the
> communications between
> the JAPL interface and its analogous I/O circuit actually happens
> so it appears
> that the MediaController is positioned behind the JAPL interface
> somewhere.
>
> The MediaController appears to be a clean communications
> mechanism that allows
> a JAPL interface to easily communicate with the physical I/O
> circuit that it
> represents so perhaps it fits the role of Adapter better?
>
> Ted
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>