[
https://issues.apache.org/jira/browse/QPID-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439179#comment-15439179
]
Rob Godfrey commented on QPID-7381:
-----------------------------------
1) My reasoning was to not add extra burden to the straight through processing
path (a simple equality check will not take observable time - whereas the
noHigher... call is linear with respect to consumers). The overwhelmingly
common case will be all consumers having the standard priority. If it comes to
pass that there is a queue with only non standard proirity consumes attached,
then it will just be the case that every delivery will go through the queue
runner.
2) Yeah - copy and paste error - will fix
3) It is, but it doesn't do any harm (I find the fact that you don't need to
start for producer connections weird)... I'd keep it the way it is
4) Yes - I think before that we should decide if we want to add some sort of
RabbitMQ compatibility feature though - their priorities work the opposite way
around (higher the better) and also allow negative numbers
5) I'd be against defining more API on Session - I'd rather people use address
strings (though I agree BURLs look weird like this)
> [Java Broker] Support consumer priorities
> -----------------------------------------
>
> Key: QPID-7381
> URL: https://issues.apache.org/jira/browse/QPID-7381
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Rob Godfrey
> Fix For: qpid-java-6.1
>
>
> Support the concept of consumer priorities. A consumer of a lower priority
> should only receive a message if there exists no consumer on the queue of a
> higher priority which has credit and would accept the message if offered it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
