zrlw commented on PR #15561: URL: https://github.com/apache/dubbo/pull/15561#issuecomment-3096699624
The content you expressed is a little difficult to understand, i try to explain it based on my own understanding. > NacosAggregateListener will aggregate all instances into each service. NacosAggregateListener aggregates instances to service instances map which grouped by service name. > every instances in NacosAggregateListener will be related to the consumerURL URL of each service when build DubboServiceAddressURL from instance and DubboServiceAddressURL#getServiceInterface is realized as ## return consumerURL.getServiceInterface() ## 1. Every service instance that NacosAggregateListener aggregated is related to the consumerURL of the service. 2. Every DubboServiceAddressURL was built from the service instance. 3. ```DubboServiceAddressURL#getServiceInterface``` method took ```DubboServiceAddressURL#getServiceInterface``` as it's return value. > every single service changed , the Subscriber will process all the service, and cache file store the all related service info. #15267 The subscriber will be notified with all service info even just one service instance status is changed, e.g., there are 3 services which names are A,B and C, the subscribe will be notified with all A,B,C service info even just one instance of service A or B or C changed. so you want change the result of ```DubboServiceAddressURL#getServiceInterface``` to limit the notification scope of dubbo service instance changing event? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
