org.apache.dubbo.registry.client

类 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>

所有已实现的接口:

Node, NotifyListener, Directory<T>

public class ServiceDiscoveryRegistryDirectory<T>
extends DynamicDirectory<T>

构造器概要

构造器

构造器和说明
ServiceDiscoveryRegistryDirectory(Class<T> serviceType, URL url)

方法概要

限定符和类型	方法和说明
boolean	isAvailable()
void	notify(List<URL> instanceUrls) Triggered when a service change notification is received.
void	subscribe(URL url)
void	unSubscribe(URL url)

从类继承的方法 org.apache.dubbo.registry.integration.DynamicDirectory

addServiceListener, buildRouterChain, destroy, discordAddresses, doList, getAllInvokers, getConsumerUrl, getInterface, getInvokers, getRegisteredConsumerUrl, getRegistry, isShouldRegister, setInvokersChangedListener, setProtocol, setRegisteredConsumerUrl, setRegistry

从类继承的方法 org.apache.dubbo.rpc.cluster.directory.AbstractDirectory

getRouterChain, getSubscribeConsumerurl, getUrl, isDestroyed, list, setConsumerUrl, setRouterChain

从类继承的方法 java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

构造器详细资料

ServiceDiscoveryRegistryDirectory

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

方法详细资料

subscribe

public void subscribe(URL url)

覆盖:

subscribe 在类中 DynamicDirectory<T>

unSubscribe

public void unSubscribe(URL url)

覆盖:

unSubscribe 在类中 DynamicDirectory<T>

isAvailable

public boolean isAvailable()

notify

public void notify(List<URL> instanceUrls)

从接口复制的说明: 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.

参数:

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