> It's good to optimize initialization of loadbalance . To my confusion : l > can't extend the SPI for ( loadbalancer.select ) when there is none or only > one invoker 。 Actually , the sortable routers can't support very well , So > that l have to accomplish a sortable composition. If some logics like alarm > notification when none or only one invoker , we can also extend the SPI ( > loadbalancer.select ) to achieve it . This is not a very good example, but it > also means better scalability.
router's route() happens before load balancer's select(). In this case, it is reasonable to return null when there's no invoker and directly return **the** invoker when there's only one. [ Full content available at: https://github.com/apache/incubator-dubbo/issues/1861 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
