/* * Copyright (c) 2014 Cisco Systems, Inc. and others. All rights reserved. * * This program and the accompanying materials are made available under the * terms of the Eclipse Public License v1.0 which accompanies this distribution, * and is available at http://www.eclipse.org/legal/epl-v10.html */ package org.opendaylight.mdsal.dom.api; import org.eclipse.jdt.annotation.NonNull; import org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode; /** * Data Broker which provides data transaction and data change listener functionality using {@link NormalizedNode}. * *
* All operations on the data tree are performed via one of the transactions: *
* These transactions provide a stable isolated view of data tree, which is guaranteed to be not * affected by other concurrent transactions, until transaction is committed. * *
* For a detailed explanation of how transaction are isolated and how transaction-local changes are * committed to global data tree, see {@link DOMDataTreeReadTransaction}, {@link DOMDataTreeWriteTransaction} * and {@link DOMDataTreeWriteTransaction#commit()}. * * *
* It is strongly recommended to use the type of transaction, which provides only the minimal * capabilities you need. This allows for optimizations at the data broker / data store level. For * example, implementations may optimize the transaction for reading if they know ahead of time that * you only need to read data - such as not keeping additional meta-data, which may be required for * write transactions. * *
* Implementation Note: This interface is not intended to be implemented by users of MD-SAL,
* but only to be consumed by them.
*/
public interface DOMDataBroker extends DOMService
* Unlike {@link #createTransactionChain(DOMTransactionChainListener)}, the transaction chain returned by this
* method is allowed to merge individual transactions into larger chunks. When transactions are merged, the results
* must be indistinguishable from the result of all operations having been performed on a single transaction.
*
*
* When transactions are merged, {@link DOMTransactionChain#newReadOnlyTransaction()} may actually be backed by
* a read-write transaction, hence an additional restriction on API use is that multiple read-only transactions
* may not be open at the same time.
*
* @param listener Transaction chain event listener
* @return A new transaction chain.
*/
@NonNull DOMTransactionChain createMergingTransactionChain(DOMTransactionChainListener listener);
}