> >How about a pluggable that could implement an adaptive algorithm, such that
> >we can let applications determine the trade offs. Something simple like a
> >min/max for starts, such that messages are absorbed by ClientConsumers
> >until
> >max, then once min has reached we refill. Or a move advanced controller
> >could implement a speed/time ratio and vary the re-fill threshold as
> >desired. Could possibly re-use some pooling logic.
> >
> >How easy would you estimate this is to remedy (short-term) and fix
> >(long-term) or perhaps they are the same...
>
> Um???
I was drinking before I wrote this ;)
> Putting in a hardcoded drop the message if non-persistent and wait if
> persistent should not be bad..
> The hard coded case will help clear up how we need to reorganize things so
> that we can make that logic plugable.
I don't understand this though... why hardcoded anything... perhaps I am
missing the point.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
