I think common users of dubbo don’t care what class represents the <dubbo:protocol>, and they don’t have to know how dubbo run. If they don’t config a port clearly, they may or may not know dubbo will pick an available port for them. But I think it’s not important that the common users do know or do not know. They can only care about if dubbo run correctly. The inner running mechanism can be transparent to the common users.
[ Full content available at: https://github.com/apache/incubator-dubbo/pull/2934 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
