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

[BIND 10 Development]

#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-20110309
  Unclassified                       |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by hanfeng):

 Hi
 > 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?
 I have add logic to avoid stop it twice.
 The server is implemented with coroutine pattern, after you close socket,
 the operator() function
 will be called again by asynchronized io process, it will continue the
 coroutine but with the error code.
 with stopped_by_hand_ ,we can quite the server as soon as possible.

 > Anyway, there are two thigs missing. The tests for this functionality
 and a proposed changelog entry.
 >
 can you enable the test? I have add the changelog
 >
 > Thanks

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