Re: REGISTRAR

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Nathan Torkington: "Re: REGISTRAR"
• Previous message: Nathan Torkington: "Re: REGISTRAR"
• In-reply-to: Nathan Torkington: "Re: REGISTRAR"
• Reply: Nathan Torkington: "Re: REGISTRAR"

Date: Sun, 11 Jul 1993 21:35:28 -0400 (EDT)
From: Rob Raisch <raisch@ora.com>
Subject: Re: REGISTRAR
To: Nathan Torkington <Nathan.Torkington@vuw.ac.nz>
Cc: www-talk@nxoc01.cern.ch
In-reply-to: <199307120123.AA10387@kauri.vuw.ac.nz>
Message-id: <Pine.3.03.9307112127.A26572-a100000@ruby.ora.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: RO

Nat, and everyone...

	I really tried to make registrar easy to understand.  It seems I
failed.  ANY questions whatsoever, please please please ask.

	I really believe that this is one of the most important issues we
have on the network today, (second only perhaps to the exhaustion of the
address space.)  

	If we cannot distribute information in an efficient fashion, as
the network grows the only answer we have to handle the increased need for
retrieval is to deploy bigger pipes.  While this is (generally) a good
thing, it swiftly becomes unmanagable.  All of this based on the fact that
we have no way to know that the file we need is on the next machine down
the line (virtually.) 

	Consider a million PDAs (Personal Data Assistants) all trying to
retrieve the same X-rated GIF of Tori Spelling or Luke Perry (never seen
it, I asked. ;) all from the same repository.  Melting the wires becomes
an understatement of epic proportions. 

	</rr>