Re: QueueFactory

Quartz wrote:
>>One of my goal is to support differents kinds of Queue. To achieve 
>>that, we must determine who is responsible to create a Queue. 
> 
> [...]
> Sure it could be pluggable, but I don't see SM nor TM dealing
> with it. Given the amount of mesures and controls related to the queue, it is part of the SM
> layer, hence the SM should crete the queue, not the TM. 

I want to be able to use queue that don't support blocking behaviour 
(think of JDK 5.0 ConcurrentLinkedQueue).  That is, a queue could 
implements *only* SinkIF and SourceIF.

Note that SourceIF is refactored to support only non-blocking methods. 
Presently, all TM use BlockingSourceIF operations, but we could create 
TM that use only SourceIF.

Because a queue could not implements BlockingSourceIF which is needed by 
some TM, a TM should be responsible to create the queue.  So, I suggest 
to add method TM.createQueue.

StageWrapperIF will continue to be responsible to add EnqueuePredicateIF 
or even decorate the queue.

Objection?
Better idea?

Jean M





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/