Re: QueueFactory

> One of my goal is to support differents kinds of Queue. To achieve 
> that, we must determine who is responsible to create a Queue. 

The SM layer is about handler choice and config (init args, admission/rate controllers,
thresholds, feedbacks)

The TM layer is about threads and runtime setup (priorities, pools sizes)

Yet, a queue is just the messenger. 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 agree with the original intent of Matt
Welsh.

I must say that you sound like you don't intent to have pluggable SM just like there is a
pluggable TM. Up to now I haven't had the need for a pluggable SM, but I would still design the
framework to be ready for it.



		
__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 



-------------------------------------------------------
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/