You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2019/10/14 01:54:34 UTC

[GitHub] [rocketmq-client-go] xujianhai666 opened a new issue #241: Client and namesrv should be exposed.

xujianhai666 opened a new issue #241: Client and namesrv should be exposed.
URL: https://github.com/apache/rocketmq-client-go/issues/241
 
 
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   expose Namesrv struct
   expose Client struct
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   I often start producer and consumer together, I want to use one client instead of each one.
   
   2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
   
   4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
   
       - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, 
       - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
       - ...
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services