BIND 10 #761: Conversion of xfrin to use the new logging interface
BIND 10 Development
do-not-reply at isc.org
Fri Jun 24 09:35:07 UTC 2011
#761: Conversion of xfrin to use the new logging interface
-------------------------------------+-------------------------------------
Reporter: | Owner: jelte
stephen | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20110628
Priority: major | Resolution:
Component: | Sensitive: 0
logging | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by stephen):
* owner: stephen => jelte
Comment:
All OK, please merge.
Concerning exceptions and messages, that is a fair point. I was thinking
more of the high-level "catch-all" clauses. Perhaps if it really is a
problem, we could do something such as including a message ID in the
exception and listing that ID in the message when the exception is caught.
At least each exception instance would be uniquely identified in a way
that might be easier for the end-user to interpret.
--
Ticket URL: <http://bind10.isc.org/ticket/761#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list