RE: [Embedlets-dev] RE: MediaController

[Ted K. <tk...@ya...>]

Chris wrote:

> 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.
[...]
> 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.

Ok, I can see this now.  I had not really thought about placing a JAPL
interface inside of another JAPL interface but I guess being able to use JAPL
interfaces anywhere (not just in Embedlets) was the reason we broke JAPL out as
a separate entity in the first place.

As for publishing a complex control component under JAPL, in my initial vision
for JAPL I had imagined them being very similar to JINI Proxy objects where the
whole (sometimes very complex) service the client is using is abstracted behind
an interface.



>If you want me to put the MediaController together, I will do that as well.

Yes, this sounds great!  I was wondering how I was going to implement the
JAPLServoController interface I had in mind but being able to use a
JAPLMediaController to do this is going to make this task much easier.

Ted

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com