Code Review / controller.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: e247eb2) | patch
BUG-7608: Clarify DOMRpc routing/invocation/listener interactions 04/51204/2
authorRobert Varga <rovarga@cisco.com>
Wed, 25 Jan 2017 21:47:02 +0000 (22:47 +0100)
committerRobert Varga <rovarga@cisco.com>
Mon, 30 Jan 2017 20:20:29 +0000 (21:20 +0100)
commit9d1222a1f001c9249f4a6b3dba6b067c65de5b4a
tree2543e19592155737090c6b14676ec460f37ed9adtree | snapshot
parente247eb2421a473c4916d6fcc3f1539707d2a2355commit | 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>
(cherry picked from commit aa342f77a044988c1f6a0deaf9f7e94373f2dfb5)
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