Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!seismo!sundc!citcom!jack
From: jack@citcom.UUCP (Jack Waugh)
Newsgroups: comp.sys.amiga
Subject: File Cache Idea
Message-ID: <50@citcom.UUCP>
Date: Mon, 10-Aug-87 22:07:01 EDT
Article-I.D.: citcom.50
Posted: Mon Aug 10 22:07:01 1987
Date-Received: Wed, 12-Aug-87 01:48:39 EDT
References: <312@l5comp.UUCP>
Organization: Citcom Systems, Inc., Herndon, VA
Lines: 17
Summary: Adding a file cache should be practical.

In article <312@l5comp.UUCP> (Re: Glossary),
 scotty@l5comp.UUCP (Scott Turner) writes:
> 3. Good ol' ram:.
> Inside this handler we have a FULL
> file system! There's code in here to
> open/close/create/delete files.
Very interesting.  This suggests it wouldn't be
that hard to provide a file cache.  Then, the
user/programmer wouldn't have to decide what
files to put in "RAM:"; the cache would.

Such a cache could usefully allow arbitrary mapping of
cache directories to real disk directories, sort of like
UN*X "mount".
 
Is it practical to write a handler without either an
assembler or a BCPL compiler, just C?