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/16 03:20:24 UTC

[GitHub] [rocketmq] qqeasonchen commented on issue #1422: [RIP-16]Support request/response pattern

qqeasonchen commented on issue #1422: [RIP-16]Support request/response pattern
URL: https://github.com/apache/rocketmq/pull/1422#issuecomment-542492927
 
 
   > [Discuss]
   > Firstly, I wonder whether need a dependent ReplyMessageProcessor here, for the reply message, I think it just is a message that needs to push to the producer directly for accelerating, so how about just implement the executeSendMessageHookBefore method for push the message directly?
   > 
   > Another, compared with just starting a consumer in the producer side to consume a reply message from the ReplyTo topic, what are the advantages of current implementation? it seems that the current practice is difficult to achieve reliable asynchronous transmission, used in scenarios where message calls cannot fail. but this implementation indeed reduced response latency, especially in the condition that ReputService is a little busy :)
   
   =====
   1. It's a  feasible way to implement with 'executeSendMessageHookBefore', Adding ReplyMessageProcessor meant to make code more clearly. Both implement is Ok.
   2. There is a problem that rebalance result would change when new instance start or old instance stop.  It is more complex to guarantee that reply message would be deliver to accurate producer.

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