BIND 10 #467: "reload zone" command for b10-auth

BIND 10 Development do-not-reply at isc.org
Thu Jan 6 23:15:52 UTC 2011


#467: "reload zone" command for b10-auth
-------------------------------------+-------------------------------------
                 Reporter:  jinmei   |                Owner:  jinmei
                     Type:  task     |               Status:  reviewing
                 Priority:  major    |            Milestone:  y2 12 month
                Component:           |  milestone
  b10-auth                           |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:7 vorner]:

 Thanks for the review.

 > There are two small things.
 >
 > The AuthSrv::io_service doesn't seem to be set anywhere (or, I did find
 no occurrence of setting it). So I guess this will cause the server to
 crash with the FatalError every time a shutdown is called on it, which
 isn't nice. Or, did I overlook something?
 >
 It's set via setIOService() from main():
 {{{
         auth_server->setIOService(io_service);
         cout << "[b10-auth] IOService created." << endl;
 }}}

 > Second one, the framework for commands looks like it could (and should)
 be shared with the recursive server. Wouldn't it be worth putting it into
 some library? Now it looks like the servers are completely independent
 products, even at places where they do nearly the same thing and the
 differences keep growing. Is it planned to be unified at some time?
 >
 Yes, I was aware of that possibility.  This stuff and (with some
 modification/generalization) the config framework will better be shared by
 both auth and recurse (or any other C++ server apps).  There's no specific
 plan for it though.  It should go to a separate task anyway, but I'll
 create a placeholder ticket for it for the record if you want.

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


More information about the bind10-tickets mailing list