BIND 10 #746: Configuration of resolver library to use the new logging interface
BIND 10 Development
do-not-reply at isc.org
Tue May 24 13:44:48 UTC 2011
#746: Configuration of resolver library to use the new logging interface
-------------------------------------+-------------------------------------
Reporter: | Owner: stephen
stephen | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20110531
Priority: minor | Resolution:
Component: | Sensitive: 0
resolver | Sub-Project: Core
Keywords: | Estimated Difficulty: 2.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => stephen
Comment:
I took the liberty of making a few trivial editorial changes to
resolvedef.mes (commit 682108d6e371706f340cfe8575d8e00d1dab09cc)
These were only editorial, and I had one suggestion for content; the RTT
output
message should probably include the unit.
General question: should we consider having a standard naming convention
for for instance DEBUG, or is something like that already included in the
final output? (i see a lot of messages where the description begins with
'debug message')
Changes look ok. I would strongly suggest we change the toText()
implementation
of Question (and probably some related ones as well) to not include the
newline.
IMO one-string/line output should not include it (this is a good example
of why). But since that requires a few more changes than just removing the
newline itself, i think we should create a separate ticket for that.
--
Ticket URL: <http://bind10.isc.org/ticket/746#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list