BIND 10 #329: When xfrin can't connect to its master, it should also the bad news to zonemgr.

[BIND 10 Development]

#329: When xfrin can't connect to its master, it should also the bad news to
zonemgr.
-----------------------------+----------------------------------------------
      Reporter:  zhanglikun  |        Owner:  jreed    
          Type:  defect      |       Status:  reviewing
      Priority:  major       |    Milestone:           
     Component:  xfrin       |   Resolution:           
      Keywords:              |    Sensitive:  0        
Estimatedhours:  1.0         |        Hours:  0        
      Billable:  1           |   Totalhours:  2.0      
      Internal:  0           |  
-----------------------------+----------------------------------------------

Comment(by jreed):

 This looks fine. (I didn't try to reproduce.) You may want to add
 comment(s) in process_xfrin() explaining this behavior. I do see docs for
 publish_xfrin_news() but I don't understand yet if xfrin itself will
 forget about it until receives a new command from zonemgr.

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