You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Jaskey Lam (JIRA)" <ji...@apache.org> on 2017/02/14 06:56:41 UTC
[jira] [Commented] (ROCKETMQ-92) Having all consumer/producer
configurations in one place
[ https://issues.apache.org/jira/browse/ROCKETMQ-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865216#comment-15865216 ]
Jaskey Lam commented on ROCKETMQ-92:
------------------------------------
I implemented this feature months ago, with a rocketmq.propties file read from classpath, is this design good for our scnenario?
> Having all consumer/producer configurations in one place
> --------------------------------------------------------
>
> Key: ROCKETMQ-92
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-92
> Project: Apache RocketMQ
> Issue Type: Improvement
> Reporter: Roman Shtykh
> Assignee: vongosling
>
> Currently, there are numerous ways how a user can specify name servers addresses for consumers/producers (see http://rocketmq.apache.org).
> This can be simplified by having all settings in one place -- for example, "{{default.conf}} file containing all default values and {{rocketmq.conf}} for application developer to override", as proposed by [~lizhanhui].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)