BIND 10 #1002: various glitches in notify_out

[BIND 10 Development]

#1002: various glitches in notify_out
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  Year
           Component:  xfrout        |  3 Task Backlog
           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
-------------------------------------+-------------------------------------
 As I worked on #964 I found various glitches in the notify_out.py
 implementation.  I suspect we'll soon need fundamentally rewrite of
 it (even if done incrementally) due to its current overall quality of
 the code, but here are some specific points as a placeholder:

 - port number 53 is hardcoded
 - creating separate sockets for separate notify transaction seems to
   be a waste
 - a related note: it's not clear whether the limit of concurrent of
   notifies (30) is reasonable.  if not, and if we allow a larger
   number notifies at the same time, the second point will be severer.
 - it's so heavily dependent on details of sqlite3 specific code
   (although not really the problem of notify_out itself)
 - it cannot send notifies to out-of-zone NSes.

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