BIND 10 #388: There's no way to close UDPServer and TCPServer.

BIND 10 Development do-not-reply at isc.org
Wed Feb 23 15:22:46 UTC 2011


#388: There's no way to close UDPServer and TCPServer.
-------------------------------------+-------------------------------------
                 Reporter:  vorner   |                Owner:  hanfeng
                     Type:  defect   |               Status:  reviewing
                 Priority:  major    |            Milestone:  A-Team-
                Component:           |  Sprint-20110223
  Unclassified                       |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => hanfeng


Comment:

 Hello

 I did small editorial fix (implicitly is when it's a sideeffect of
 something, there were extra spaces on the ends of lines).

 What happens if the server is stopped twice? Will it be nop, or it will
 crash? Why is the stopped_by_hand_ needed anyway? Do you expect a packet
 to come after the socket is closed?

 Anyway, there are two thigs missing. The tests for this functionality and
 a proposed changelog entry.

 About the test I mentioned ‒ one is inside the auth server (well, in the
 #575, it is moved to separate library). But it depends on DNSService's
 clearServers method, which should call the stop of all servers. And maybe
 there's a disabled test for this method in asiolink as well. Should I have
 a look at those and enable them?

 Thanks

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


More information about the bind10-tickets mailing list