saz97 commented on PR #9549: URL: https://github.com/apache/rocketmq/pull/9549#issuecomment-3077039389
> If the scheduled pull is not retained, this method strongly relies on the client, and the client and server must be upgraded together. In fact, in actual production applications, many client and server versions are inconsistent, because the cost of upgrading the client is very high. Is compatibility considered in this way? Thank you for your valuable insights and the practical perspective from production environments! I’ll retain the client’s periodic route-pulling mechanism as a fallback, ensuring compatibility across different client/server versions. -- 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]
