BIND 10 #862: Properly encapsulate the output buffer in AbstractMessageRenderer

[BIND 10 Development]

#862: Properly encapsulate the output buffer in AbstractMessageRenderer
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 As discussed in #404, we shouldn't expose the output buffer to descendants
 of `AbstractMessageRenderer` trough `getBuffer()`. The most problematic
 place that uses it is name compression in `MessageRenderer`, which needs
 some small refactoring. The rest should be trivial to replace.

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