Caching

Kevin Small <small@netcom.com> Sun, 05 December 1993 01:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06129; 4 Dec 93 20:41 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06125; 4 Dec 93 20:41 EST
Received: from mocha.bunyip.com by CNRI.Reston.VA.US id aa16186; 4 Dec 93 20:41 EST
Received: by mocha.bunyip.com (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA00424 on Sat, 4 Dec 93 19:39:48 -0500
Received: from netcom3.netcom.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA00420 (mail destined for /usr/lib/sendmail -odq -oi -fiafa-request iafa-out) on Sat, 4 Dec 93 19:39:40 -0500
Received: from localhost by mail.netcom.com (8.6.4/SMI-4.1/Netcom) id QAA12236; Sat, 4 Dec 1993 16:39:36 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Small <small@netcom.com>
Message-Id: <199312050039.QAA12236@mail.netcom.com>
Subject: Caching
To: Internet Anonymous FTP Archives <iafa@bunyip.com>
Date: Sat, 04 Dec 1993 16:39:36 -0800
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Length: 766

There is a need for cache servers and distribution servers.  The
overall effeciency of the Internet would benefit from there use.
There would need to be a way to ensure that the data the server had
was current.  This could be accomplished by using "content signatures"
which are 64 bit numbers (32 bit filesize field + 32 bit crc field).
See the document FWKCS120.REF in the DOS Shareware program
FWKCS120.ZIP for information regarding "content signatures".

Existing client programs could take advantage of the cache servers by
making their queries through the servers.

But even if the data had changed it would be preferrable to just move
the changes across the Internet.


-- 
Kevin Small
small@netcom.com
-rw-------  1 small          55 Sep 24 14:55 .signature