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

diff --git a/doc/design/resolver/02-mixed-recursive-authority-setup b/doc/design/resolver/02-mixed-recursive-authority-setup
index 81d80e3c426340a20bb3d28df900dc0deb180a4d..c53912493b617544261e88e4b9d19a5beafea52c 100644 (file)
--- 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