BIND 10 #3296: Rethink Pkt4 and Pkt6 class hierarchy

BIND 10 Development do-not-reply at isc.org
Fri Jan 17 19:42:23 UTC 2014


#3296: Rethink Pkt4 and Pkt6 class hierarchy
-------------------------------------+-------------------------------------
                   Reporter:  tomek  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP
                   Priority:         |  Outstanding Tasks
  medium                             |              Keywords:
                  Component:  dhcp   |             Sensitive:  0
               CVSS Scoring:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 There are many similarities between Pkt4 and Pkt6, but they do not have a
 common base class. Furthermore, some methods in both classes are server-
 specific (e.g. relay manipulation code) that would be useless on the
 client side.

 We should rethink the class hierarchy here. One possible way forward would
 be:

 BasePkt->Pkt4->SrvPkt4
 BasePkt->Pkt6->SrvPkt6

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


More information about the bind10-tickets mailing list