BIND 10 #735: Investigate BIND-9 Logging

[BIND 10 Development]

#735: Investigate BIND-9 Logging
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  stephen
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20110503
  critical                           |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  logging                            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => stephen


Comment:

 Hello

 It is true the logging has quite similar interface and the wrapper in the
 experiment is quite thin. So yes, it could be used and it is probably
 better than writing our own.

 But there are still some issues, you mentioned some of them (problems with
 runtime adding and removing of loggers, need have a copy in git and CVS or
 something), some of you didn't, like the need to pass and update
 configuration online. And how much is it flexible? If we wanted to have
 some other fancy logging destination (eg. sending over msgq to a
 component, printing it on line printer, ...), would it be hard?

 Also, I don't like dragging in the whole library just because of logging.
 In general, I personally prefer using something generally available (eg.
 external library), because we don't need to maintain it and it can be
 reused in the system by something else.

 On the other hand, is there anything else in the library useful for us?

 In short, this is better than writing it ourself, but I like some log4cxx
 more I guess, even if it has some build problems. Or what was the problem
 with that one again?


 I guess there's no reason to point out issues regarding the experimental
 code, right?

 Anyway, should we close this, or discuss it on some call or something? I'm
 never sure with tickets that say „investigate“, with the coding ones it's
 easy, when it's merged, its done.

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