FYI for those openwire watchers.
I just added a 'noRangeAcks' flag to the ConsumerInfo command. Not
really used yet, but I figure it may be useful in the future and I'd
rather get these small flags in before 4.0 goes final. The broker may
be able to optimize it's processing or provides better QOS if it knows
the consumer will not be sending ranged acks.
A simple use case is to allow messages to be reordered based on
priority while it's sitting in queues post the broker dispatch stage.
If the client is doing ranged acks, reordering would not be allowed
since the order the client receives the messages must match the order
that the broker dispatched them in so that it acks the right messages
in the ack range.
--
Regards,
Hiram
