package org.opendaylight.controller.cluster.datastore;
import akka.actor.ActorSelection;
-import com.google.common.base.Optional;
import com.google.common.util.concurrent.SettableFuture;
-import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier;
-import org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode;
+import org.opendaylight.controller.cluster.datastore.messages.AbstractRead;
+import org.opendaylight.controller.cluster.datastore.modification.AbstractModification;
import scala.concurrent.Future;
/*
Future<ActorSelection> readyTransaction();
- void writeData(YangInstanceIdentifier path, NormalizedNode<?, ?> data);
+ void executeModification(AbstractModification modification);
- void deleteData(YangInstanceIdentifier path);
+ <T> void executeRead(AbstractRead<T> readCmd, SettableFuture<T> promise);
- void mergeData(YangInstanceIdentifier path, NormalizedNode<?, ?> data);
+ Future<Object> directCommit();
- void readData(final YangInstanceIdentifier path, SettableFuture<Optional<NormalizedNode<?, ?>>> proxyFuture);
+ /**
+ * 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.
+ *
+ * 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.
+ */
+ void operationHandOffComplete();
- void dataExists(YangInstanceIdentifier path, SettableFuture<Boolean> proxyFuture);
+ /**
+ * A TransactionContext that uses Operation limiting should return true else false
+ * @return
+ */
+ boolean usesOperationLimiting();
+
+ short getTransactionVersion();
}