On 04/16/2010 10:29 AM, Andrew Kennedy wrote:
a proper description of the meaning of ACL rules is also required,
since it is not always clear what the intent of rules and ordering
might be. the only documentation i could find is here:
http://qpid.apache.org/acl.html#ACL-userguide
I agree that some detailed documentation would be good for what we
currently have. There have also been some change requests via Jira and
I'm sure there are some other ideas out there on what should be added.
One of the issues I would like to hear thoughts around is evolving the
permissions model with minimal disruption for existing users.
i will try and use the same error text as the C++ parser, but these
should probably be standardised somewhere (again, i may just not have
been able to find this). also, error recovery is not very well defined
- i would be interested to know what people's position is on broker
behavior with invalid or badly-formed ACL configurations. there are a
few possibilities:
1. exit the broker immediately with an exception.
2. record the error and start the broker with a best effort at
parsing the file, ignoring the rule (and possibly even all following
rules).
3. record the error and start the broker with an empty ACL
configuration that ALLOWS all access.
4. record the error and start the broker with an empty ACL
configuration that DENIES all access.
i believe 2 is desirable, but 1 is easiest. depending on requirements,
3 or 4 could be configurable behaviours after errors.
I think 1 is a good approach. As well as being easy it is clear to the
user. Good error messages will make fixing the error simple and will
result in a better overall user experience in my view.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
