The reason that the dispatch needs to be paused on the Server side is for a Quality of Service Broker to control the message dispatch if the network traffic gets to be too much. This is similar to the client Pre-Fetch Limit, except the messages are measured and controlled on servicer hosting the Active MQ instance, and not the client.
We want to create a server-side implementation of the prefetch limit. Instead of using the client acknowledgements to control messaging, we want to use QoS service parameters on the Server to pause the dispatch. I can provide more details if you wish. ============= James.Strachan wrote: > > On 2/3/07, jkurtz <[EMAIL PROTECTED]> wrote: >> We are interested in pausing the message transmission periodically from >> outside of Active MQ, while allowing incoming messages to accumulate. >> Modifying the source code is an option, and we are looking at the >> transport >> class. >> >> >> Does anyone know if this is feasible without major revisions of the code? > > Could you explain a little bit more as to why you want to do this? > > With the use of prefetch, messages are only dispatched to consumers > when they have spare capacity anyway (so dispatching stops if a > consumer pauses) > > http://activemq.apache.org/what-is-the-prefetch-limit-for.html > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Pausing-Transmission-tf3167927.html#a8818110 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
