Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!texbell!texsun!newstop!sun!quintus!pds
From: pds@quintus.UUCP (Peter Schachte)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Resident, Pipes, Alias & ARP
Message-ID: <1283@quintus.UUCP>
Date: 14 Nov 89 21:52:19 GMT
References: <245612@neabbs.UUCP>
Reply-To: pds@quintus.UUCP (Peter Schachte)
Organization: Quintus Computer Systems, Inc.
Lines: 27

In article <245612@neabbs.UUCP> ajbrouw@neabbs.UUCP (ALBERT-JAN BROUWER) writes:
 > I suppose Fred puts his S: into RAD: in order to get extra speed when executing
>scripts.  So why not enhance the resident command (I use ARP) in order to allow
>users to make script files resident?.

Actually, you can almost do this now yourself.  You can use the PATH
device (which came of c.s.a a while back) to allow you to assign S:  to
first RAM:S and then SYS:S.  So when you try to execute a script, it
first looks in RAM:S and then, if it can't find it, in SYS:S.

Unfortunately, this won't automatically cache a script in ram the first
time you use it, you'll have to copy it there yourself.  Worse, though,
is that any program that tries to write into S: will fail.  And you
can't do a dir of S:.

Maybe what's needed here is a CACHE:  device, that lets you specify
files to cache, loads them into memory the first time you read them, and
then reads them from memory thereafter.  Of course, it would manage LRU
dumping of the cache, and would handle out-of-memory conditions.

It's amazing what you can do with devices (if you can only figure out
how to write them)!

-- 
-Peter Schachte
pds@quintus.uucp
...!sun!quintus!pds