BIND 10 #401: Timouts in the recursor

[BIND 10 Development]

#401: Timouts in the recursor
--------------------------+-------------------------------------------------
  Reporter:  vorner       |            Owner:     
      Type:  enhancement  |           Status:  new
  Priority:  major        |        Milestone:     
 Component:  recurser     |         Keywords:     
 Sensitive:  0            |   Estimatedhours:  0  
     Hours:  0            |         Billable:  1  
Totalhours:  0            |         Internal:  0  
--------------------------+-------------------------------------------------
 I implemented basic support of timeouts in the b10-recurse.

 The most important part is in UDPQuery (which asks upstream DNS server a
 question, will probably be used in some similar form by the dispatch),
 that can report a timeout now. The RecursiveQuery can retry few times
 before giving up.

 Currently, it needs a merge with the branch from #389 to be configurable.
 Furthermore, some of the current code is temporary until the merge is done
 (the #389 contains a DNSService without any sockets, for example).

 The timeouts are configured only statically for now (no computing of
 average timeout, increasing timeouts when a packet is lost, etc). Do you
 think it should be done now or some time later?

 The proposed changelog entry would be:

 {{{
 [func]  vorner
 b10-recurse supports timeouts and retries in forwarder mode.
 (trac #401, SVN rTBD)
 }}}

 Code is in branches/vorner-recursor-timeouts, branch point r3392.

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