On Wed, Aug 24, 2016 at 1:13 PM, Robert Varga <n...@hq.sk> wrote:
> On 08/24/2016 01:06 PM, Tom Pantelis wrote: > > Yes but accessing it via getSupportedExtensions isn't intuitive, hence > > the discussion. > > Well, it follows the Extensible Object pattern, which really is the only > feasible way to provide extensibility without breaking API contracts in > face of multiple competing contracts and forwarding classes... > Well I do think there is another way.. with Dependency Injection, you can create additional interfaces for new API methods, and then register a single service implementation under several Service API interfaces, to make it easy for clients to get them inject easily instead of having to grab one thing and in client code having to adapt them to another thing explicitly à la getSupportedExtensions().get(...), assuming that's what you mean with the Extensible Object pattern. So as I said, I'd second & +1 "to also advertise the PingPongDataBroker instance with the DOMDataTreeChangeService interface".
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
