BIND 10 #740: Conversion of asiolink library to use new logging interface

[BIND 10 Development]

#740: Conversion of asiolink library to use new logging interface
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20110712
                   Priority:  major  |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:5 jelte]:
 > The current asiolink library does not print or log anything, so there's
 nothing to convert.
 >
 > Still putting this up for review for a second opinion; do we do nothing
 or do we add the logging setup but with an empty message file? In the case
 of the second, we'd put in an empty message file, making it easier to add
 debug messages should we want to. OTOH, it's also easy to do that the
 moment we do decide we want to, so i'm leaning towards doing nothing atm).

 I agree, based on the sense of YAGNI.  I'd also note that there are
 other module(s) that don't have logging framework (e.g., libdns++), so
 this discussion can be generalized to other cases.  My suggestion is
 to close this one for now, and create a separate meta (placeholder)
 ticket that lists a known modules that currently lack logging and may
 need to be revised, and put it to the backlog so that we can revisit
 it later.

 Whether there's really nothing to log in the ASIO link module is a
 separate question.  I actually suspect there are some (such as for
 some unexpected communication failures).  If we see the need for it
 quite clearly right now, we can immediately create a dedicated ticket
 for that work (but in any case it's not "conversion" so I'm okay with
 deferring it to a separate ticket).

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