org.opendaylight.controller.sal.core.api

Interface BrokerService

All Known Subinterfaces:

DOMDataBroker, DOMDataTreeService, DOMDataTreeShardingService, DOMExtensibleService<T,E>, DOMMountPointService, DOMNotificationPublishService, DOMNotificationService, DOMRpcProviderService, DOMRpcService, DOMService, SchemaService, TracingDOMDataBroker

All Known Implementing Classes:

AbstractBrokerServiceProxy, AbstractDOMDataBroker, AbstractDOMRpcProviderService, BrokerImpl, ConcurrentDOMDataBroker, DOMDataBrokerProxy, DOMMountPointServiceImpl, DOMMountPointServiceProxy, DOMNotificationRouter, DOMRpcRouter, ForwardingDOMDataBroker, ForwardingDOMNotificationPublishService, ForwardingDOMNotificationService, ForwardingDOMRpcProviderService, ForwardingDOMRpcService, GlobalBundleScanningSchemaServiceImpl, LegacyShardedDOMDataBrokerAdapter, PingPongDataBroker, SchemaServiceProxy, SerializedDOMDataBroker, ShardedDOMDataTree, TracingBroker

public interface BrokerService

Session-specific instance of the broker functionality.

BrokerService is marker interface for infrastructure services provided by the SAL. These services are session-specific, each Provider and Consumer usually has own instance of the service with it's own context.

The consumer's (or provider's) instance of specific service could be obtained by invoking Broker.ConsumerSession.getService(Class) method on session assigned to the consumer.

BrokerService and Provider may seem similar, but provider provides YANG model-based functionality and BrokerService exposes the necessary supporting functionality to implement specific functionality of YANG and to reuse it in the development of Consumers and Providers.