[
https://issues.apache.org/jira/browse/QPID-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159926#comment-17159926
]
Robert Godfrey commented on QPID-8455:
--------------------------------------
[~DedeepyaT] Thanks for your patch, but as per the discussion between myself
and Alex above, we cannot just change the names without providing some way for
existing users to maintain compatibility. Any patch / PR needs to take this
into account - minimally by also incrementing the configuration model version
and adding an upgrade step to the model upgraders to update the config files
for existing users.
> [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
>
> Attachments:
> 0001-QPID-8455-Broker-J-Use-allow-deny-list-terminology-f.patch
>
>
> 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
