Package org.apache.dubbo.registry.client

Class ServiceDiscoveryRegistryDirectory<T>

java.lang.Object
org.apache.dubbo.rpc.cluster.directory.AbstractDirectory<T>
org.apache.dubbo.registry.integration.DynamicDirectory<T>
org.apache.dubbo.registry.client.ServiceDiscoveryRegistryDirectory<T>
All Implemented Interfaces:
Node, NotifyListener, Directory<T>
public class ServiceDiscoveryRegistryDirectory<T> extends DynamicDirectory<T>

  • Constructor Details

    • ServiceDiscoveryRegistryDirectory

      public ServiceDiscoveryRegistryDirectory(Class<T> serviceType, URL url)

  • Method Details

    • subscribe

      public void subscribe(URL url)
      Overrides:
      subscribe in class DynamicDirectory<T>

    • unSubscribe

      public void unSubscribe(URL url)
      Overrides:
      unSubscribe in class DynamicDirectory<T>

    • destroy

      public void destroy()
      Specified by:
      destroy in interface Node
      Overrides:
      destroy in class DynamicDirectory<T>

    • buildRouterChain

      public void buildRouterChain(URL url)
      Overrides:
      buildRouterChain in class DynamicDirectory<T>

    • notify

      public void notify(List<URL> instanceUrls)
      Description copied from interface: NotifyListener
      Triggered when a service change notification is received.

      Notify needs to support the contract:
      1. Always notifications on the service interface and the dimension of the data type. that is, won't notify part of the same type data belonging to one service. Users do not need to compare the results of the previous notification.
      2. The first notification at a subscription must be a full notification of all types of data of a service.
      3. At the time of change, different types of data are allowed to be notified separately, e.g.: providers, consumers, routers, overrides. It allows only one of these types to be notified, but the data of this type must be full, not incremental.
      4. If a data type is empty, need to notify a empty protocol with category parameter identification of url data.
      5. The order of notifications to be guaranteed by the notifications(That is, the implementation of the registry). Such as: single thread push, queue serialization, and version comparison.

      Parameters:
      instanceUrls - The list of registered information , is always not empty. The meaning is the same as the return value of RegistryService.lookup(URL).

    • isServiceDiscovery

      public boolean isServiceDiscovery()

    • isNotificationReceived

      public boolean isNotificationReceived()
      This implementation makes sure all application names related to serviceListener received address notification.

      FIXME, make sure deprecated "interface-application" mapping item be cleared in time.

      Specified by:
      isNotificationReceived in interface Directory<T>
      Overrides:
      isNotificationReceived in class DynamicDirectory<T>

    • toString

      public String toString()
      Overrides:
      toString in class AbstractDirectory<T>