frankjkelly commented on PR #853: URL: https://github.com/apache/pulsar-client-go/pull/853#issuecomment-1260812367
> Yes, this is where the current Go SDK design is worth optimizing. In the Go SDK, we implemented the reconnect logic to the Producer side and the Consumer side respectively, and did not abstract a unified reconnect logic at the Client level. This leads to the Backoff strategy, we can only divide it into ProducerOptions and ConsumerOptions. In the follow-up, I think we should refactor here and abstract the logic of reconnect to the client side, which is more reasonable Thanks - sounds good - this is fine for our use-case as is -- 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]
