Bug 7795: Do not prescribe notification throttling mechanism 84/52884/2
authorVratko Polak <vrpolak@cisco.com>
Mon, 6 Mar 2017 14:01:10 +0000 (15:01 +0100)
committerTom Pantelis <tpanteli@brocade.com>
Mon, 6 Mar 2017 16:54:12 +0000 (16:54 +0000)
uses NotificationPublishService#putNotification
which returns void, not Future.

Change-Id: I88c3898b014820168d5748174c9112daa42acbde
Signed-off-by: Vratko Polak <vrpolak@cisco.com>

index e9a6c7a..4c08715 100644 (file)
@@ -127,9 +127,7 @@ module odl-mdsal-lowlevel-control {
     rpc publish-notifications {
         description "Upon receiving this, the member shall start publishing llt:id-sequence
             notifications with the given id and sequence numbers, increasing, from 1.
-            .get with a timeout on currently earliest non-complete Future (from .publish)
-            shall be used as the primary wait method to throttle the publish rate.
-            The RPC shall not return until all publishes are confirmed successful,
+            The RPC shall not return until all publishes are successful,
             or an exception is raised (the exception should propagate to restconf response).";
         input {
             uses llc:id-grouping;

©2013 OpenDaylight, A Linux Foundation Collaborative Project. All Rights Reserved.
OpenDaylight is a registered trademark of The OpenDaylight Project, Inc.
Linux Foundation and OpenDaylight are registered trademarks of the Linux Foundation.
Linux is a registered trademark of Linus Torvalds.