[
https://issues.apache.org/jira/browse/QPID-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866122#action_12866122
]
Andrew Kennedy commented on QPID-2539:
--------------------------------------
1. I'd like to emphasize again that there should not be a separate c++ and java
ACL file formats. We should have one and only one ACL file format for Qpid
brokers. If we agree to make changes, then both brokers would need to support
it.
There are users who are already trying to use both C++ and Java brokers (using
federation) in production. Having a single file format makes life very easy
here.
2. Qpid as project is aiming to provide a consistent experience across all
brokers and clients. This is a vision and a goal of this project. Individual
features should be developed with this in mind.
3. IMO having a strict format is better, as it is simple and less ambiguous,
resulting in far less errors. Also rigid format is better for a security
related to system to prevent people from exploiting the lenient nature of the
format to exploit any gaps.
ADK: I agree. The 'less strict' phrasing was not the best choice of words. The
file format I'm proposing still has no ambiguity, and can be defined with a
strict EBNF grammar (if so desired ;) and is simply an extension of the C++
format, i.e. any valid C++ broker ACL file is also a valid Java broker ACL
file. The opposite is not true, since at the moment there are features
(virtualhosts) that are not available in the C++ broker. Actually, this can be
dealt with the same way the java broker deals with currently un-implemented
features (routes, links) by ignoring those ACL stanzas.
> Update ACL file syntax to be clearer and add extra operations
> -------------------------------------------------------------
>
> Key: QPID-2539
> URL: https://issues.apache.org/jira/browse/QPID-2539
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Broker
> Reporter: Andrew Kennedy
> Fix For: 0.7
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
