BIND 10 #1086: Ensure message consistency when outputting address+port or name+type+class

[BIND 10 Development]

#1086: Ensure message consistency when outputting address+port or name+type+class
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  enhancement   |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  logging       |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130402
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  2             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 You missed the logging output, which were quite a few more :p

 Anyway, ready for review;

 In the python code, I added an AddressFormatter class, similar (but not
 equal) to the ClientFormatter in ddns.logger; we *could* consider basing
 the one in ddns on this new one but it takes very different input and has
 different extra option, so I left it alone for now.

 For the few cases in C++ i did not create such a class as yet, these are
 outside of critical paths and had different inputs anyway. But I guess we
 could consider doing something similar.

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