BIND 10 #489: Config timeouts: receiving response, stop trying, stop for specific client

[BIND 10 Development]

#489: Config timeouts: receiving response, stop trying, stop for specific client
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  jelte
                     Type:           |               Status:  closed
  enhancement                        |            Milestone:  R-Team-
                 Priority:  major    |  Sprint-20110208
                Component:           |           Resolution:  fixed
  resolver                           |            Sensitive:  0
                 Keywords:           |  Add Hours to Ticket:  0
Estimated Number of Hours:  2.0      |          Total Hours:  0
                Billable?:  1        |
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 well, given the current way runningquery works, these are created and live
 until they are either done or fail, having no timeouts at all is a memory
 leak (and a dos if timeout is set too high). One currently half-baked idea
 is having a fixed set of available runningquery objects to use (and
 probably drop the oldest one if we run out), which would be more efficient
 and solve that specific problem.

 for the defaults there is a ticket already (#518), will create the other
 task later (perhaps warrants a bit of discussion on what it would look
 like and where the task would fit)

 Merged, closing ticket.

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