Re: Caching

Kevin Small <> Mon, 06 December 1993 07:41 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa00761; 6 Dec 93 2:41 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00757; 6 Dec 93 2:41 EST
Received: from by CNRI.Reston.VA.US id aa23245; 6 Dec 93 2:41 EST
Received: by (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01796 on Mon, 6 Dec 93 01:00:05 -0500
Received: from by with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01792 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Mon, 6 Dec 93 00:59:59 -0500
Received: from localhost by (8.6.4/SMI-4.1/Netcom) id WAA06542; Sun, 5 Dec 1993 22:00:10 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Small <>
Message-Id: <>
Subject: Re: Caching
Date: Sun, 5 Dec 1993 22:00:09 -0800 (PST)
Cc: Internet Anonymous FTP Archives <>
In-Reply-To: <755135250/vac@FURMINT.NECTAR.CS.CMU.EDU> from "Vincent.Cate@FURMINT.NECTAR.CS.CMU.EDU" at Dec 5, 93 05:00:18 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 749

Vincent.Cate@FURMINT.NECTAR.CS.CMU.EDU writes:
> I think Alex is very much like what you are looking for.
> Alex is a filesystem that gives you access to anonymous FTP files.  It
> does do caching of files.  If the size of the file and the date last
> modified have not changed, Alex assumes that the cached copy is still
> good.  I don't know of any cases where this has been a problem.  The
> real question is how often do you want to check that your cached data
> is current.  

On demand verification might do the trick.

Caching must be an integral part of networking.  Networking can
continue without it, but it will be grossly inefficient.  Not just
files, but any data that traverses the network.

Kevin Small