In response to your situation, dubbo provides a router to solve, you can dynamically configure on dubbo-ops.
The client itself is not likely to be unaware of the server. The behavior of P1 forwarding a request to P2 itself is meaningless. Because we could have the Consumer send the corresponding request directly to the corresponding Provider. Increasing the number of transfers means increasing the risk. As far as I know, no RPC framework implements this functionality on the server side. [ Full content available at: https://github.com/apache/incubator-dubbo/issues/2639 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
