BIND 10 #1075: Rewording of CC and DATASRC messages

[BIND 10 Development]

#1075: Rewording of CC and DATASRC messages
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20110712
                   Priority:  minor  |            Resolution:
                  Component:         |             Sensitive:  0
  logging                            |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => UnAssigned
 * status:  assigned => reviewing


Comment:

 > CONFIG_CCSESSION_MSG_INTERNAL -- what module "will continue to run"? and
 reword "An unexpected exception was thrown." so is useful to admin reading
 this.
 This was already changed.

 > DATASRC_CACHE_CREATE "creating" (upcoming) or "created" (already done)?
 and what debug level for DATASRC_CACHE_CREATE?
 I'll leave it as "CREATE".  The message is issued in the constructor and
 until that exits, the cache can't really be said to have been created.

 > DATASRC_CACHE_DESTROY being destroyed -- does that mean it is a long
 process?
 Issued just prior to deleting the cache implementation object, so "being
 destroyed" is strictly correct.

 > DATASRC_ some say "cache" and others "hotspot cache" -- are they really
 different?
 Used interchangeably.

 > reword DATASRC_CACHE_OLD_FOUND, older instance of cache item found,
 replacing to "replacing existing cache item" and is it useful if doesn't
 indicate the name or its value?
 The name of the item found has been added.  As the message will be issued
 after DATASRC_CACHE_INSERT (and not as a standalone message), the message
 text seems appropriate.

 > DATASRC_MEM_ADD_WILDCARD: reword "Some special marks above each * in
 wildcard name are needed."
 Reworded.

 > DATASRC_MEM_CNAME_TO_NONEMPTY -- what about DNSSEC records?
 There is an "XXX" (now renamed to TODO) in the code to revisit this when
 DNSSEC is added.

 > DATASRC_META_ADD description is not completed.
 Reworded.

 > what is a "meta data source"?
 I ''think'' it is a data source that can comprise multiple data sources.
 However, the !MetaDataSrc class in data_source.h has no header comments so
 that is only a guess.

 > DATASRC_QUERY_EMPTY_CNAME description is not completed.
 Reworded.

 > DATASRC_QUERY_IS_* "a query" (add "a")?
 Added.

 > DATASRC_QUERY_PROVENX_FAIL and others What does "PROVENX" mean? (spell
 out "NONEXISTENCE"?)
 Changed to "DATASRC_QUERY_PROVE_NX_FAIL"; NONEXISTENCE seems a bit too
 long a word to fit into the message ID.

 > reword DATASRC_QUERY_SYNTH_CNAME description
 Altered.

 > DATASRC_SQLITE_PREVIOUS_NO_ZONE what is purpose to identify preceding
 name if not in same zone?
 I ''think'' that this is part of the searching for the closest match (the
 method that
 generates it has no header comments).  If (for example) www.isc.org is not
 found, then a search is made for isc.org and then for org.  The
 description for this message (and the similar DATASRC_SQLITE_PREVIOUS)
 have been updated.


 > generic DATASRC_STATIC_BAD_CLASS ID but description is for a specific
 class

-- 
Ticket URL: <http://bind10.isc.org/ticket/1075#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development