avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emperor" <DarkEmpe...@gmx.net>
Subject AW: QueueElement interface
Date Thu, 28 Mar 2002 13:30:19 GMT


> -----Ursprüngliche Nachricht-----
> Von: Berin Loritsch [mailto:bloritsch@apache.org] 
> Gesendet: Donnerstag, 28. März 2002 14:25
> An: 'Avalon Developers List'
> Betreff: RE: QueueElement interface
> 
> 
> > -----Original Message-----
> > From: Emperor [mailto:DarkEmperor@gmx.net]
> 
> > Hi,
> > 
> > What is the QueueElement interface good for? Wouldn't it be
> > better to use Object instead of it in order to allow queuing 
> > of final classes and java objects you can't modify?
> 
> The QueueElement interface is lifted from Matt Welsh's 
> SandStorm implementation of the SEDA architecture.  It may 
> not be necessary, but typically we want to have a message 
> class of some sort that references the "Objects" we want to 
> enqueue.  It gives them context, and simplifies the 
> EventHandler implementation.

Ok, I agree it's cleaner, but I think this is limiting the possibilities
of the queue implementations.

> 
> 
> > 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 
> > manager soon. I need help to reorganize, find typos and 
> > integrate to avalon...
> 
> Ok.  I need to move the event stuff into the main excalibur 
> area anyway...
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:avalon-dev-help@jakarta.apache.org>
> 
> 


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message