Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 96121 invoked from network); 4 Dec 2003 23:58:18 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Dec 2003 23:58:18 -0000 Received: (qmail 39850 invoked by uid 500); 4 Dec 2003 23:58:03 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 39788 invoked by uid 500); 4 Dec 2003 23:58:03 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 39767 invoked from network); 4 Dec 2003 23:58:02 -0000 Received: from unknown (HELO imf19aec.mail.bellsouth.net) (205.152.59.67) by daedalus.apache.org with SMTP; 4 Dec 2003 23:58:02 -0000 Received: from franklin ([65.81.198.151]) by imf19aec.mail.bellsouth.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031204235810.WAVG1942.imf19aec.mail.bellsouth.net@franklin> for ; Thu, 4 Dec 2003 18:58:10 -0500 From: "Alex Karasulu" To: "'Apache Directory Developers List'" Subject: RE: [eve] Event Manager Date: Thu, 4 Dec 2003 18:58:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcO6tyiifMo+gDMjSFai2g2sdggWLgACp0dQ Message-Id: <20031204235810.WAVG1942.imf19aec.mail.bellsouth.net@franklin> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > > > > You could have a look at the implementation of this pattern I > > > mentioned in a previous mail. At least you'll save yourself > > > a lot of javadoc ;-). > > > > Does it follow the conventions in the link you already sent? > > Yes it does. Then we'll start borrowing from it. I just got back and have some repo things to do to get the old stuff to compile. Then I'm off to work on the setting up this event stuff which we all can work on. I'll start pulling over some of your event bus code decoupling it from the Swing. > That's the trick. The asynchronous event manager republishes event on > the bus asynchronously through a queue. It uses a CricularEventFilter > to avoid receiving events the events it has republished. That's cool - no need to reinvent the wheel (excuse the slight pun). > > Here's the link to that doc again and to Vincent's sf.net effort: > > > > http://members.ispwest.com/jeffhartkopf/notifier/ > > Here's the implementation: > > http://cvs.sourceforge.net/viewcvs.py/d-haven/guiapp/guiapp- > core/src/java/or > g/d_haven/guiapp/eventbus/ > > You will need to remove the Swing related stuff (only a couple of lines > though). Great will do. > > For the time being we'll model the service using Avalon life-cycle > > methods and target Merlin. Slowly as we begin to get leads for the > Pico, > > Loom, and Phoenix containers we can add adapters for them. > > I don't want to waste too much time messing with containers but have > > their adapters prepared in the background. I'm thinking Vincent you're > > Pico container proficient > > If you say so ;-0 > > > so you go ahead and get a Pico adapter > > setup for > > it if you like or when you have the time. > > I will learn tips and tricks of Picoyification on the AAA bits > and then we can apply all over. That sounds like a plan. Hopefully after that I can give a general Breakdown of the backend setup so we can start Picoyificamationing :-) there. Ok we got plans. Alex