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

[BIND 10 Development]

#862: Properly encapsulate the output buffer in AbstractMessageRenderer
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  vorner                             |                Status:  assigned
                       Type:  task   |             Milestone:
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  Unclassified                       |  Estimated Difficulty:  0.0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:2 shane]:
 > Michal, we've had a lot of refactoring recently, including the way
 MessageRenderer is used. Do you think this ticket still makes sense?

 I think we still need to consider this.  The latest version (in the
 branch) of renderer still
 refers to the internal buffer

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