Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 59397 invoked from network); 4 Dec 2003 22:25:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Dec 2003 22:25:14 -0000 Received: (qmail 84974 invoked by uid 500); 4 Dec 2003 22:25:02 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 84908 invoked by uid 500); 4 Dec 2003 22:25:01 -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 84891 invoked from network); 4 Dec 2003 22:25:01 -0000 Received: from unknown (HELO mail.devtech.com) (66.112.202.2) by daedalus.apache.org with SMTP; 4 Dec 2003 22:25:01 -0000 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.2.0-dev) with SMTP ID 786 for ; Thu, 4 Dec 2003 17:25:06 -0500 (EST) From: "Noel J. Bergman" To: "Apache Directory Developers List" Subject: RE: [eve] Event Manager Date: Thu, 4 Dec 2003 17:25:01 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <200312041531.05283.wmckean@logictrends.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal 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 > I really like the Event Notifier Pattern. May I take a stab at this? FWIW, I like it to ... which is why I wrote an implementation of the CORBA COS Event Service years ago in C++. Also, Vince pointed to one, which assuming that the license is compatible, would be at least a start. > 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. An Event Channel, to use COS Event Service terms, manages a particular set of registered suppliers and consumers. Both pull and push processing are supported for both suppliers and consumers. How you do that is up to you, but I found it useful to maintain a queue for each pull consumer. --- Noel