RE: [Embedlets-dev] Re: JAPL Events

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

>
> > > An embedlet should be able to register itself as a listener to a JAPL
> > > event generator
> >
> > I strongly disagree.  This couples JAPL and Embedlets too much and
> bypasses
> > the Embedlet Event scheduling and control mechanisms.  Bad idea.  If you
> are
> > doing that, then why bother with a container?  Just write straight Java
> code
> > and be done with it.
>
> Not to mention cause the JAPL events to grind to a (almost) halt
> waiting for
> the Outpost container(s) to do what they need to do!.
>

I think that Andrzej has addressed this:

Embedlets need to know about JAPL not the other way around.
Embedlets (or the JAPLEventProducer) register as JAPLEventListeners to
receive async notification

If we agree on the portability criteria as the functional dividing line
there is little overlap and everyone keeps on truckin'.

Chris

> - Brill Pappin
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>