[
https://issues.apache.org/jira/browse/DISPATCH-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112186#comment-17112186
]
Ted Ross commented on DISPATCH-1659:
------------------------------------
One problem with "proper" JSON is that comments cannot be included in the text.
I'm not sure how much of a problem this is but it was a major consideration in
the selection of the current format.
If we're considering making an incompatible change to the config format, we
should probably also consider using YAML for the new format.
> Deprecate bespoke config file format for proper JSON
> ----------------------------------------------------
>
> Key: DISPATCH-1659
> URL: https://issues.apache.org/jira/browse/DISPATCH-1659
> Project: Qpid Dispatch
> Issue Type: Wish
> Components: Management Agent
> Affects Versions: 1.12.0
> Reporter: Ken Giusti
> Priority: Minor
> Fix For: 2.0.0, Backlog
>
>
> The format of the qdrouterd.config file is not JSON compliant. Instead it is
> some bespoke quasi subset of JSON with custom comment syntax and whitespace
> formatting restrictions.
> This bespoke format has (at least) two disadvantages:
> 1) users cannot leverage the plethora of JSON tooling available for config
> generation
> 2) increased development/maintenance effort to support the bespoke format.
> This is a proposal to deprecate support for the non-JSON configuration file
> format in favor of a JSON compliant file format.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
