From owner-freebsd-hackers Sun Jun 23 19:02:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA12438 for hackers-outgoing; Sun, 23 Jun 1996 19:02:26 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA12431 for ; Sun, 23 Jun 1996 19:02:23 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id LAA02491; Mon, 24 Jun 1996 11:02:03 +0900 (JST) Date: Mon, 24 Jun 1996 11:02:03 +0900 (JST) From: Michael Hancock To: Mattias Pantzare cc: denis , freebsd-hackers@FreeBSD.ORG Subject: Re: Dynamically Allocatable Name Service (DANS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 23 Jun 1996, Mattias Pantzare wrote: > > I'd like to hear how he plans to handle servicing dynamic updates and name > > requests with the performance required. BIND once initialized operates > > entirely in RAM and the service has high performance requirements that are > > hard to meet even with a static database. > > I think that you are missing the point. What he is doing is to store the > names that the nameserver provides to other servers in a database instead > of in a textfile. Not to do the name caching on disk. The whole binary > database can be cached in RAM. I understand what can be done. Rocket and bike analogies just makes it sound like name serving is a trivial exercise. mike hancock -- Speaking for myself.