Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 410 invoked from network); 28 Mar 2002 13:30:21 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 28 Mar 2002 13:30:21 -0000 Received: (qmail 5953 invoked by uid 97); 28 Mar 2002 13:30:20 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 5937 invoked by uid 97); 28 Mar 2002 13:30:20 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 5925 invoked from network); 28 Mar 2002 13:30:19 -0000 From: "Emperor" To: "'Avalon Developers List'" Subject: AW: QueueElement interface Date: Thu, 28 Mar 2002 14:30:19 +0100 Message-ID: <000601c1d65c$b522da20$1e4b8350@EMPEROR> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <000f01c1d65b$f8b1bb90$ac00a8c0@Gabriel> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Urspr=FCngliche Nachricht----- > Von: Berin Loritsch [mailto:bloritsch@apache.org]=20 > Gesendet: Donnerstag, 28. M=E4rz 2002 14:25 > An: 'Avalon Developers List' > Betreff: RE: QueueElement interface >=20 >=20 > > -----Original Message----- > > From: Emperor [mailto:DarkEmperor@gmx.net] >=20 > > Hi, > >=20 > > What is the QueueElement interface good for? Wouldn't it be > > better to use Object instead of it in order to allow queuing=20 > > of final classes and java objects you can't modify? >=20 > The QueueElement interface is lifted from Matt Welsh's=20 > SandStorm implementation of the SEDA architecture. It may=20 > not be necessary, but typically we want to have a message=20 > class of some sort that references the "Objects" we want to=20 > enqueue. It gives them context, and simplifies the=20 > EventHandler implementation. Ok, I agree it's cleaner, but I think this is limiting the possibilities of the queue implementations. >=20 >=20 > > I had much to do in the last weeks but I think I'll have the > > time to release the first version of the async connection=20 > > manager soon. I need help to reorganize, find typos and=20 > > integrate to avalon... >=20 > Ok. I need to move the event stuff into the main excalibur=20 > area anyway... >=20 >=20 > -- > To unsubscribe, e-mail: =20 > unsubscribe@jakarta.apache.org> > For=20 > additional commands,=20 > e-mail: >=20 >=20 -- To unsubscribe, e-mail: For additional commands, e-mail: