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 2020/04/28 16:24:43 UTC

[GitHub] [rocketmq-client-go] xujianhai666 opened a new issue #476: [Native] improve async send impl

xujianhai666 opened a new issue #476:
URL: https://github.com/apache/rocketmq-client-go/issues/476


   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   user broker abstract instead of conn map
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   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



[GitHub] [rocketmq-client-go] xujianhai666 commented on issue #476: [Native] improve async send impl

Posted by GitBox <gi...@apache.org>.
xujianhai666 commented on issue #476:
URL: https://github.com/apache/rocketmq-client-go/issues/476#issuecomment-620946921


   async send & send should block on one goroutine of broker, broker just scan range future, which got after send, therefore async producer never need a goroutine to block on timeout


----------------------------------------------------------------
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