BIND 10 #2265: cleanup: remove Renderer::clear() calls

BIND 10 Development do-not-reply at isc.org
Tue Sep 18 06:15:03 UTC 2012


#2265: cleanup: remove Renderer::clear() calls
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:
                       Type:  task   |                Status:  new
                   Priority:         |             Milestone:  Next-Sprint-
  medium                             |  Proposed
                  Component:         |            Resolution:
  Unclassified                       |             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      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 What's the goal of this ticket?  Remove unnecessary calls to
 `MessageRenderer.to_wire` from xfrout?  Remove such calls throughout
 the source code?  Is it Python or C++ or both (the :: notation seems
 to indicate C++, but #1357 is for xfrout, which is written in Python)?

 BTW, if it's for python, I've been thinking we might provide an
 enhancement to `Message.to_wire()` so it can use an internal
 `MessageRenderer` and directly returns a byte sequence.  Then the code
 will be much more simplified like this:

 {{{#!python
     s.send(msg.to_wire(compress_mode=CASE_SENSITIVE,
                        truncation_limit=65535,
                        tsig_ctx=if_using_tsig))
 }}}

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


More information about the bind10-tickets mailing list