[
https://issues.apache.org/jira/browse/QPID-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158770#comment-17158770
]
Alex Rudyy commented on QPID-8455:
----------------------------------
[~rgodfrey], I am considering to do the changes in the bug fix release and
leave the old names (as alternative names) for the backward compatibility.
Thus, the existing users should be able to use old names, if required. I am
thinking about adding alternativeNames property into statistics and attribute
annotations. That should allow to specify various synonyms for the
attributes/context variables in order to keep backward compatibility. The
alternative names can be even returned as part of REST API output together with
the real names. I think, that major version release is required for the
attribute name changes. That's why I am thinking about introduction of
mechanism for the alternative names. What do you think about this idea?
> [Broker-J]Use allow/deny list terminology for existing attributes and context
> variables
> ---------------------------------------------------------------------------------------
>
> Key: QPID-8455
> URL: https://issues.apache.org/jira/browse/QPID-8455
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Dedeepya
> Priority: Major
> Fix For: qpid-java-broker-8.0.1, qpid-java-broker-7.1.9
>
>
> Rename attributes and context variables containing the term white/black list
> to allow/deny list.
> The names allow/deny list are more inlined with current industry naming
> standards.
> Example:
> The port derived attributes tlsCipherSuiteWhiteList and
> tlsCipherSuiteBlackList will have to be renamed to tlsCipherSuiteAllowList
> and tlsCipherSuiteDenyList respectively.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
