Fix TransactionContextWrapper limiter accounting
[controller.git] / opendaylight / md-sal / sal-distributed-datastore / src / main / java / org / opendaylight / controller / cluster / datastore / TransactionContext.java
index 1e23120f0bf6b833ff395b2a5863c6795ff65da7..543834c2cbad2547e33352b8a43dd9e55b399912 100644 (file)
@@ -20,19 +20,20 @@ import scala.concurrent.Future;
 interface TransactionContext {
     void closeTransaction();
 
-    Future<ActorSelection> readyTransaction();
+    Future<ActorSelection> readyTransaction(Boolean havePermit);
 
-    void executeModification(AbstractModification modification);
+    void executeModification(AbstractModification modification, Boolean havePermit);
 
-    <T> void executeRead(AbstractRead<T> readCmd, SettableFuture<T> promise);
+    <T> void executeRead(AbstractRead<T> readCmd, SettableFuture<T> promise, Boolean havePermit);
 
-    Future<Object> directCommit();
+    Future<Object> directCommit(Boolean havePermit);
 
     /**
      * Invoked by {@link TransactionContextWrapper} when it has finished handing
      * off operations to this context. From this point on, the context is responsible
      * for throttling operations.
-     * <p/>
+     *
+     * <p>
      * Implementations can rely on the wrapper calling this operation in a synchronized
      * block, so they do not need to ensure visibility of this state transition themselves.
      */