I meant ComponentModel below sorry. > -----Original Message----- > From: Alex Karasulu [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 10, 2004 12:14 PM > To: 'Avalon Developers List' > Subject: RE: Event mechanism in Merlin > > > > > -----Original Message----- > > From: Nader Aeinehchi [mailto:[EMAIL PROTECTED] > > Sent: Friday, April 09, 2004 5:18 PM > > To: Avalon Developers List > > Subject: Re: Event mechanism in Merlin > > > > 1. Please forgive me for my ignorance, but is the difference facility > and > > custom lifecycle extension? What is a facility? > > Steve explained this to me the other day. It's a component that has > access > to the CompositionModel as a special Context. So it can affect other > components and provide services for other components. > > > > To me, an event-driven component > > > is a kissing cousin to a message-driven component, so I think a merlin > > > plug-in facility would handle this quite nicely. > > > > 2. Just for clarity, we are talking about asynchronous messages among > > various objects and components? Are not we? > > I keep things synchronous with events while build SEDA stages that the > events are enqueued on. You can always do asynchronous from synchronous > but > going synchronous from asynchronous is harder. I'd keep it simple and > synchronous. > > > 3. In Jini, there is Distributed Events. Is this something that should > be > > taken into consideration to handle events among various JVMs? > > Maybe but I have not thought that far yet. I'm just using this for > decoupling components so I can avoid cyclic dependencies. > > Alex > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
