BIND 10 #2023: xfrin doesn't send the right command to zonemgr after transfer

[BIND 10 Development]

#2023: xfrin doesn't send the right command to zonemgr after transfer
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  high          |                    Milestone:  Next-
           Component:  xfrin         |  Sprint-Proposed
           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
-------------------------------------+-------------------------------------
 From code inspection, it seems to send the 'notify' command
 (= notify_out.ZONE_NEW_DATA_READY_CMD) while it should actually send
 'zone_new_data_ready' (= zonemgr.ZONE_XFRIN_SUCCESS_COMMAND)
 (see publish_xfrin_news()).

 It should be fixed, and the fix should be trivial.  The bigger problem
 is that it seems to me yet another incident of the current xfr-related
 things are so broken in various ways (ugly implementation, luck of
 tests, ad hoc design architecture, command naming conflict, etc), but
 for now, let's fix the immediate problem.

 I also suspect this is a background reason for #1786 and #1834.

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