From: JINMEI Tatuya <jinmei@isc.org>
Date: Tue, 26 Feb 2013 04:43:29 +0000 (-0800)
Subject: [res-design] added some small idea for the hybrid auth/resolver server
X-Git-Tag: bind10-1.2.0beta1-release~404^2~3
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc735da7e6210f87e4e5a36fce91eb990b8bbbc8;p=thirdparty%2Fkea.git

[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 81d80e3c42..c53912493b 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