Hi, @diecui1202 After looking at the code, I think we really have to consider compatibility issues.
After thinking, I think it would be better if you fix this problem at both ends. 1. On the Provider side, the method.async is not exposed to ensure compatibility. 2. Ignore the Provider's method.async property on the Consumer side to ensure that the Provider's method.async does not affect the Consumer's behavior. In the future, when OPS shows the asynchronous situation of the provider, we just need to let the provider still register the method.async property. What do u think? [ Full content available at: https://github.com/apache/incubator-dubbo/issues/2321 ] This message was relayed via gitbox.apache.org for [email protected]
