From: Mukund Sivaraman Date: Thu, 13 Jun 2013 09:13:08 +0000 (+0200) Subject: [2776] Minor tweaks and fixes X-Git-Tag: bind10-1.2.0beta1-release~404^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3a98bed98afbf27ec36a941936d1bf11c656178d;p=thirdparty%2Fkea.git [2776] Minor tweaks and fixes --- diff --git a/doc/design/resolver/02-mixed-recursive-authority-setup b/doc/design/resolver/02-mixed-recursive-authority-setup index 33750a5a01..a1cc5f66ef 100644 --- a/doc/design/resolver/02-mixed-recursive-authority-setup +++ b/doc/design/resolver/02-mixed-recursive-authority-setup @@ -5,7 +5,7 @@ Ideally we will run the authoritative server independently of the recursive resolver. We need a way to run both an authoritative and a recursive resolver on -a single platform, listening on the same IP/port. But we need a way to +the same machine and listening on the same IP/port. But we need a way to run only one of them as well. This is mostly the same problem as we have with DDNS packets and xfr-out @@ -22,7 +22,7 @@ With some build system or dynamic linker tricks, we create three modules: * Stand-alone resolver * Compound module containing both -The user then chooses either one stand alone module, or the compound one, +The user then chooses either one stand-alone module, or the compound one, depending on the requirements. Advantages @@ -36,7 +36,7 @@ Disadvantages * The code is not separated (one bugs takes down both, admin can't see which one takes how much CPU). - * Bind 9 does this and bind 9 code is a jungle. Maybe it's not just a + * BIND 9 does this and its code is a jungle. Maybe it's not just a coincidence. * Limits flexibility -- for example, we can't then decide to make the resolver threaded (or we would have to make sure the auth processing doesn't break @@ -62,7 +62,7 @@ Advantages Disadvantages ~~~~~~~~~~~~~ - * Counter-intuitive asymetric design + * Counter-intuitive asymmetric design * Possible slowdown on the resolver side * Resolver needs to know both modes (for running stand-alone too) @@ -81,7 +81,7 @@ forwarded to the resolver. The resolver then updates the cache too. Advantages ~~~~~~~~~~ - * Probably a good performance + * Probably good performance Disadvantages ~~~~~~~~~~~~~ @@ -135,7 +135,7 @@ Implementation ideas * The queries are sent from the receptionist in batches, the answers are sent back to the receptionist in batches too. * It is possible to fine-tune and use OS-specific tricks (like epoll or - sending multiple UDP messages by single call to sendmmsg). + sending multiple UDP messages by single call to sendmmsg()). Proposal --------