qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-1617) ACLv2 cannot allow only queue browsers
Date Fri, 18 Jul 2014 21:50:08 GMT

     [ https://issues.apache.org/jira/browse/QPID-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Keith Wall resolved QPID-1617.

    Resolution: Won't Fix

Agreed in a product backlog review - won’t fix.

> ACLv2 cannot allow only queue browsers
> --------------------------------------
>                 Key: QPID-1617
>                 URL: https://issues.apache.org/jira/browse/QPID-1617
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Martin Ritchie
>              Labels: ACLs
> Summary:
> The ACL specification was designed to be very close to the protocol as a result the extension
performed by the Java client/broker to enable JMS QueueBrowsing is not currently reflected
in the specification.
> As the ability to browse is handled differently in 0-8/9, 0-10 and 1-0 but it would be
good if we could have a configuration that would work across versions.
> Having a common configuration mechanism will be important if the Java broker is going
to be supporting multiple protocol versions simultaneously. 
> If it was just 0-8/9 I would suggest we add a property 'no_consume' to the consume action
which can be used by the broker to control the browser. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message