RE: [Embedlets-dev] Re: JAPL Events

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

____________________________________________
> 
> Chris says (welcome back Chris!):
> 
> > I think that Andrzej has addressed this:
> > 
> > Embedlets need to know about JAPL not the other way around.
> 
> That I agree with wholeheartedly.
> 
> > Embedlets (or the JAPLEventProducer) register as JAPLEventListeners to
> > receive async notification
> 
> Not quite.  I am very uncomfortable with an Embedlet registering 
> as a JAPLEventListener 
> and then having callbacks issued on the Embedlet. I can think of 
> certain container 
> implementations where this could be problematic.  I suggest that 
> the creation of a proxy 
> class (JAPLWrapper) that registers as a JAPLEventListener and 
> then proxies the data into 
> the Embedlet world as an Embedlet Event is a much better solution 
> architecturally.
> 
Agreed 

> > If we agree on the portability criteria as the functional dividing line
> > there is little overlap and everyone keeps on truckin'.
> 
> True enough.
> 
> ...Andrzej
> 
> Chaeron Corporation
> http://www.chaeron.com
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb: 
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>