Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <007901c41e78$2fa49300$fe01a8c0@corp.4tel.no>
From: "Nader Aeinehchi" <nader@aeinehchi.com>
To: "Avalon Developers List" <dev@avalon.apache.org>
References: <c56s5r$vdr$1@sea.gmane.org>
 <20040409190746.HNGC1702.imf16aec.mail.bellsouth.net@franklin>
 <c56tip$2vr$1@sea.gmane.org>
Subject: Re: Event mechanism in Merlin
Date: Fri, 9 Apr 2004 23:18:20 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

1. Please forgive me for my ignorance, but is the difference facility and
custom lifecycle extension?  What is a facility?


> 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?

3. In Jini, there is Distributed Events.  Is this something that should be
taken into consideration to handle events among various JVMs?


Best Regards

--
Nader Aeinehchi
Aasenhagen 66 E
2020 Skedsmokorset
NORWAY
Direct and Mobile +47 41 44 29 57
Tel (private): +47 64 83 09 08
Fax +47 64 83 08 07
www.aeinehchi.com

----- Original Message -----
From: "Timothy Bennett" <exterminatorx@comcast.net>
To: <dev@avalon.apache.org>
Sent: Friday, April 09, 2004 9:23 PM
Subject: Re: Event mechanism in Merlin


> Alex Karasulu wrote:
>
> >>-----Original Message-----
> >>From: news [mailto:news@sea.gmane.org] On Behalf Of Timothy Bennett
> >>Sent: Friday, April 09, 2004 2:59 PM
> >>To: dev@avalon.apache.org
> >>Subject: Re: Event mechanism in Merlin
> >>
> >>Alex Karasulu wrote:
> >>
> >>
> >>>What do you think about creating a custom lifecycle for the subscribe
> >>>Operation on this event router/bus concept.  BTW Berin has already done
> >>>this with GUIApp but I'd like to see this sort of thing make its way
> >>>into Merlin.
> >>>
> >>
> >>Alex, IMO I think this is better done as a facility instead of a custom
> >>lifecycle extension.  In the way that we are doing HTTP-driven
> >>components and (JMS) message-driven components using facilities, I think
> >>a facility to implement event-driven components is a good candidate.
> >
> >
> > Hmmm that does make more sense.  I think I agree with you.
> >
> > Alex
>
> This is basically the path that will be (is being) taken with Aaron's
> MDS (Message-Driven Service) stuff.  In it's first incarnation, MDS was
> an Avalon framework lifecycle extension that basically allowed you to
> define a special custom component that was *triggered* by a JMS message.
>   Good stuff and I used it some in the pre-3.2.x Merlin distros.
>
> With the advent of the facility capabilities in the more recent Merlin
> versions, Aaron has thrown the MDS stuff into the facilities arena, and
> we plan to implement an MDS facility.  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.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org