Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
From: Wes McKean <wmckean@logictrends.com>
Organization: Logic Trends
To: directory-dev@incubator.apache.org
Subject: [eve] Event Manager
Date: Thu, 4 Dec 2003 15:31:05 -0500
User-Agent: KMail/1.5.4
References: <20031204193434.OWPE1936.imf25aec.mail.bellsouth.net@franklin>
 <200312041456.40159.wmckean@logictrends.com>
In-Reply-To: <200312041456.40159.wmckean@logictrends.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200312041531.05283.wmckean@logictrends.com>

I really like the Event Notifier Pattern.  May I take a stab at this?  If so, 
should I write it for Merlin?  Or should I create something generic that can 
be imbedded in any container?  The container could then implement a standard 
interface or something.

Here's my idea...

The Event Manager will establish a queue for the events.  I'm thinking one 
queue is fine, just like in the pattern, although there may be a benefit to 
using multiple queues ( one for every event type ), please comment.

There is a single thread monitoring the queue.  When an event gets placed into 
the queue, the thread picks it up, creates or gets a worker thread from the 
pool, then goes through the subscribers, notifying each one of the event.

The subscriber may or may not have its own thread pool.  We don't care :-)

Let me know...  Looks like it could be fun.

Wes