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:  jelte
  stephen                            |                Status:  closed
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20110712
                   Priority:  major  |            Resolution:  complete
                  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      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * status:  reviewing => closed
 * resolution:   => complete


Comment:

 Replying to [comment:6 jinmei]:
 >
 > 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.
 >

 Not sure about whether we need a meta ticket, you can quite quickly see
 which modules have a messages file and which don't. I did put a short
 message about it in the README, so it's at least marked that we didn't
 forget about this module.

 > 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).

 Yes we might find something to log, I suspect that would be mostly for
 debugging purposes, and we can jsut add them as we find the need for it.

 Closing ticket.

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