BIND 10 #495: Hook up NSAS to iterator/cache

[BIND 10 Development]

#495: Hook up NSAS to iterator/cache
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  UnAssigned
                     Type:           |               Status:  reviewing
  enhancement                        |            Milestone:  R-Team-
                 Priority:  major    |  Sprint-20110308
                Component:           |           Resolution:
  resolver                           |            Sensitive:  0
                 Keywords:           |  Add Hours to Ticket:  0
Estimated Number of Hours:  3.0      |          Total Hours:  0
                Billable?:  1        |
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 it's alive! ALIVE!!!
 (and ready for review)

 notable changes that were needed for the actual implementation:
 - removed the 'dummy' asiolink from nsas (it even had a different api than
 the real one!)
 - removed a few unused parameters in asio (!) and asiolink
 - move recursive_query itself to lib/resolve
 - added NXRRSET result (name exists, but no data for this type) to the
 possible classifications in response_classifier
 - lots of changes in RunningQuery (naturally, one would almost say)
 - added a 'fake prime' to resolver; just a hardcoded packet to initialize
 the cache with a root address

 parent of the first commit is ba727c17d3517232a3c40fa3a30c6924a30ed7dc
 current head is 87308eeddf767dea581b817d1d2ab2aaa4a99dd3

 There are some open todo's, but I think we should have those as separate
 tasks (so as not to make this one bigger than it already is):
 - RecursiveQuery and RunningQuery (both of which could use a rename btw),
 get quite a lot of arguments, i think we should have something like an
 ResolverOptions class for most of these.
 - General cleanup of RunningQuery; mainly moving methods and names around
 (didn't do this now so you can still diff the old
 lib/asiolink/recursive_query.cc and the new lib/resolve/recursive_query
 and see what the actual changes are now)
 - Real priming (does not need to be extensive, just something that
 actually sends a priming query when needed and caches the result)
 - Add control and configuration options for the cache (cache_size, flush,
 etc)
 - This ticket add the use of the NSAS, but it isn't perfect yet i think
 (i.e. general recursive behaviour)
 - We need to define what exactly to do when in 'forwarder' mode
 - and of course glue correction, which is already a ticket

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