Nader, Over on the directory side we're actually using subversion but here's the link to the repo:
http://cvs.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/frontend/eve nt/?root=Apache-SVN Oh and BTW this is just another component - although I'd like to explore the use of it as a facility. Just don't seem to have the time at the moment while working to get Eve out of the incubator. Cheers, Alex > -----Original Message----- > From: Nader Aeinehchi [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 21, 2004 5:15 PM > To: Avalon Developers List > Subject: Re: Event mechanism in Merlin > > Hello > > Could someone tell me the CVS location of the event component in eve > project? > > Thanks. > > 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: "Nader Aeinehchi" <[EMAIL PROTECTED]> > To: "Avalon Developers List" <[EMAIL PROTECTED]> > Sent: Friday, April 09, 2004 11:18 PM > 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? > > > > > > > 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" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, April 09, 2004 9:23 PM > > Subject: Re: Event mechanism in Merlin > > > > > > > Alex Karasulu wrote: > > > > > > >>-----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] > > > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
