[
https://issues.apache.org/jira/browse/TUBEMQ-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240677#comment-17240677
]
Guocheng Zhang commented on TUBEMQ-430:
---------------------------------------
During the analysis process, in the implementation of the HTTP API:
# the source code defines parameters at tempely，the same parameter should have
the same field attribute requirements in any API interface, the parameter
prorietis should not be temporarily set in every place;
# at the same time, for the failure matching of the same rule, the error
message should output the same error expression instead of redefining a content
for each error;
# for the API interface of the broker, it should be possible to extend some
common business information, such as lagging information, and should Support
call through CLI command.
> Optimizing the implementation of HTTP API for broker
> ----------------------------------------------------
>
> Key: TUBEMQ-430
> URL: https://issues.apache.org/jira/browse/TUBEMQ-430
> Project: Apache TubeMQ
> Issue Type: Improvement
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
>
> At present, there are some problems in the HTTP API implementation, such as
> API encapsulation is not perfect, readability is poor, and some consumption
> related metrics are missing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
