Code Review / controller.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a373730) | patch
BUG-7608: Clarify DOMRpc routing/invocation/listener interactions 34/51034/4
authorRobert Varga <rovarga@cisco.com>
Wed, 25 Jan 2017 21:47:02 +0000 (22:47 +0100)
committerTom Pantelis <tpanteli@brocade.com>
Mon, 30 Jan 2017 13:45:01 +0000 (13:45 +0000)
commitaa342f77a044988c1f6a0deaf9f7e94373f2dfb5
tree9c56346c5af915565b937bfd29196e10811d903dtree | snapshot
parenta3737302942580f13ca9988647873b83985895edcommit | diff
BUG-7608: Clarify DOMRpc routing/invocation/listener interactions

As it happens our DOMRpcProviderService is under-documented around
routing behavior and how it interacts with respect to both
DOMRpcService and DOMRpcAvailabilityListener.

Fix this by defining the interactions the same way they are implemented
in the only implementation, DOMRpcRouter.

The fallout of these clarifications is that blueprint's interpretation
of the API contract covers only the RFC6020 RPC part correctly and falls
short of the RFC7950 action case.

This shortcoming will be addressed in a follow-up patch.

Change-Id: I2572c21b7aa6f24b9e2ed37f446b76a032f1880b
Signed-off-by: Robert Varga <rovarga@cisco.com>
opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/md/sal/dom/api/DOMRpcAvailabilityListener.java diff | blob | history
opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/md/sal/dom/api/DOMRpcProviderService.java diff | blob | history
opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/md/sal/dom/api/DOMRpcService.java diff | blob | history
OpenDaylight controller