-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Bennett Sent: Friday, April 09, 2004 2:59 PM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
