yanrongzhen commented on PR #4544: URL: https://github.com/apache/eventmesh/pull/4544#issuecomment-1797923873
> > Could you explain how this PR solves the problem described in issue #4178? Because most of the code I see seems to be a unified and abstract refactoring of the code related to the grpc, http, and tcp modules. > > 能否解释下该PR是怎么解决issue #4178所描述的问题？因为我看到的代码好像大部分是给grpc、http、tcp三个模块相关代码做统一和抽象的重构工作。 > > Waiting for your reply. First of all, the goal of this PR is to provide the ability to retry in the MQ retry queue within the Retry module. Here are two changes made: 1. The `EventMeshProducer`, `ProducerManager`, and `SendMessageContext` of each protocol have been standardized. The reason for this change is that Retry should be a standard processing method, regardless of the specific underlying protocol, and the usage of these three protocols is completely consistent, so they are merged. 2. In RetryContext, when the user turns on the switch, the message is sent to the retry queue asynchronously to retry. --- 首先, 此PR的目标是在Retry模块内部提供于MQ重试队列来进行重试的能力. 这里做了两个改动: 1. 对于各协议的EventMeshProducer, ProducerManager, SendMessageContext进行了标准化, 此改动的原因是Retry应该是一个标准的处理方式, 而不关心具体底层的协议, 并且这三者在各协议的用法完全一致, 因此进行了合并处理. 2. 在RetryContext中, 在用户打开开关时, 支持将消息异步发送至重试队列中, 以达到重试的效果. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
