Re: Caching

Kevin Small <small@netcom.com> Mon, 06 December 1993 07:41 UTC

Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Small <small@netcom.com>
Message-Id: <199312060600.WAA06542@mail.netcom.com>
Subject: Re: Caching
To: Vincent.Cate@furmint.nectar.cs.cmu.edu
Date: Sun, 05 Dec 1993 22:00:09 -0800
Cc: Internet Anonymous FTP Archives <iafa@bunyip.com>
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
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
small@netcom.com

Caching Kevin Small
Re: Caching Mike Schwartz
Re: Caching Mark A. Constable
Re: Caching Vincent.Cate
Re: Caching Kevin Small
Re: Caching Kevin Small
Re: Caching Vincent.Cate