From: Mukund Sivaraman <muks@isc.org>
Date: Mon, 21 Jan 2013 06:47:40 +0000 (+0530)
Subject: [2435] Explain why using the rrset collection is not allowed after calling ZoneUpdate... 
X-Git-Tag: bind10-1.0.0-rc-release~87
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=631366a33bb06d01547c0789edfadde7a17228bd;p=thirdparty%2Fkea.git

[2435] Explain why using the rrset collection is not allowed after calling ZoneUpdater::commit()
---

diff --git a/src/lib/datasrc/zone.h b/src/lib/datasrc/zone.h
index 45f7545b2e..3b720ae96c 100644
--- a/src/lib/datasrc/zone.h
+++ b/src/lib/datasrc/zone.h
@@ -825,9 +825,11 @@ public:
     /// because iterating the collection may result in unexpected
     /// behavior if the underlying data is updated.  Implementations of
     /// \c ZoneUpdater may disable a previously returned
-    /// \c RRsetCollection after \c commit() is called. If an
-    /// \c RRsetCollection is disabled, using methods such as \c find() and
-    /// using its iterator would cause an exception to be thrown. See
+    /// \c RRsetCollection after \c commit() is called. Even in this
+    /// case, using existing iterators may result in unexpected behavior
+    /// after \c commit() is called. If an \c RRsetCollection is
+    /// disabled, using methods such as \c find() and using its iterator
+    /// would cause an exception to be thrown. See
     /// \c isc::datasrc::RRsetCollectionBase for details.
     virtual isc::datasrc::RRsetCollectionBase& getRRsetCollection() = 0;