Date: Mon, 24 Jun 1996 11:02:03 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Mattias Pantzare <pantzer@ludd.luth.se> Cc: denis <denis@actcom.co.il>, freebsd-hackers@FreeBSD.ORG Subject: Re: Dynamically Allocatable Name Service (DANS) Message-ID: <Pine.SV4.3.93.960624104116.2140C-100000@parkplace.cet.co.jp> In-Reply-To: <Pine.SUN.3.91.960623171212.7099A-100000@mother.ludd.luth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.93.960624104116.2140C-100000>