BIND 10 #740: Conversion of asiolink library to use new logging interface
BIND 10 Development
do-not-reply at isc.org
Wed Jun 29 14:38:31 UTC 2011
#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 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
* status: assigned => reviewing
Comment:
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).
--
Ticket URL: <http://bind10.isc.org/ticket/740#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list