Hi, Another item I was thinking of from the JMS point of view was QueueBrowsing. Currently the Java Broker with 0-8/9 uses a custom property 'no_consume' to determine that the new consumer should be a browser. Ideally we should be able to control this independently from queue consumption with the ACLs however that is not currently possible.
I've JIRA'd the fact (QPID-1617) and one possible solution of using a no_consume property. However, I wasn't sure how this would work with 0-10 or even 1-0. It would be good to get a format that we can use in all of the protocol versions. I imagine it would be quite difficult/confusing to configure the ACLs in the Java broker (when we support multiple version) if we need a special queue browsing acl for each protocol version. Thoughts on the best way to represent a queue browser in the acl file? Of course that is all dependant on the ability to determine that a connecting user is actually a browser in 0-10 / 1-0 and not just a consumer that hasn't yet consumed. Checking to ensure the acquire mode is NOT_AQUIRED would seem like a possible solution. Regards Martin -- Martin Ritchie
