From: JINMEI Tatuya <jinmei@isc.org>
Date: Tue, 19 Feb 2013 17:37:03 +0000 (-0800)
Subject: [2676] remove the comment about using "protected" member in __notify_update.
X-Git-Tag: bind10-1.1.0beta1-release~83^2~5
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3bec0f1f82f1bbc2a296cb40999047421abcba94;p=thirdparty%2Fkea.git

[2676] remove the comment about using "protected" member in __notify_update.

the revised code eliminated its use as a side effect.
---

diff --git a/src/bin/ddns/ddns.py.in b/src/bin/ddns/ddns.py.in
index 223128bacc..d382495e49 100755
--- a/src/bin/ddns/ddns.py.in
+++ b/src/bin/ddns/ddns.py.in
@@ -587,13 +587,6 @@ class DDNSServer:
         For a longer term we'll need to switch to asynchronous communication,
         but for now we rely on the blocking operation.
 
-        Note also that we directly refer to the "protected" member of
-        ccsession (_cc._session) rather than creating a separate channel.
-        It's probably not the best practice, but hopefully we can introduce
-        a cleaner way when we support asynchronous communication.
-        At the moment we prefer the brevity with the use of internal channel
-        of the cc session.
-
         '''
         try:
             # FIXME? Is really rpc_call the correct one? What if there are more