BIND 10 resolver_research_and_design, updated. 70cc3db9edd5e1b30d8efb8107e57de021fdaac3 [res-design] added some small idea for the hybrid auth/resolver server

[BIND 10 source code commits]

The branch, resolver_research_and_design has been updated
       via  70cc3db9edd5e1b30d8efb8107e57de021fdaac3 (commit)
      from  5d221a4027cdd09be11a45cd30bea2ef5b67bbed (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 70cc3db9edd5e1b30d8efb8107e57de021fdaac3
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Mon Feb 25 20:43:29 2013 -0800

    [res-design] added some small idea for the hybrid auth/resolver server

-----------------------------------------------------------------------

Summary of changes:
 .../resolver/02-mixed-recursive-authority-setup    |    3 +++
 1 file changed, 3 insertions(+)

-----------------------------------------------------------------------
diff --git a/doc/design/resolver/02-mixed-recursive-authority-setup b/doc/design/resolver/02-mixed-recursive-authority-setup
index 81d80e3..c539124 100644
--- a/doc/design/resolver/02-mixed-recursive-authority-setup
+++ b/doc/design/resolver/02-mixed-recursive-authority-setup
@@ -18,6 +18,9 @@ We have 3 basic components involved in this mix:
 There are a number of possible approaches to this:
 
 a. Make a module that includes all logic. (The BIND 9 module?)
+a'. extract major processing logic of auth into a separate library
+   (maybe loadable module) and allow the resolver to use it, probably
+   as a kind of hook.
 b. Look at authoritative server first, and pass queries to the
    recursive component.
 c. Make a module that combines authoritative and cache. Queries not