Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!think!ames!lll-tis!ptsfa!lll-lcc!well!perry
From: perry@well.UUCP (Perry S. Kivolowitz)
Newsgroups: comp.sys.amiga
Subject: Re: AutoFacc (binary and doc)
Message-ID: <3320@well.UUCP>
Date: Mon, 15-Jun-87 09:37:55 EDT
Article-I.D.: well.3320
Posted: Mon Jun 15 09:37:55 1987
Date-Received: Sun, 21-Jun-87 02:09:05 EDT
References: <8580@amdahl.amdahl.com>
Lines: 39
Keywords: facc autofacc shrink add delete buffers cli executable ASDG
Summary: FaccII Won't Require AutoFacc


Boy you guys don't give a fella a chance (:-)

AutoFacc is a  nice idea (haven't  downloaded it  yet  though) but won't be
needed on FaccII.  When that comes out you'll find that Facc has been split
into (sometimes) two processes. The reason the original Facc didn't support
command line  arguments  is that I tore out the usual Manx startup stuff to
save space in Facc (I was  already upset that the Inuition stuff took up 10
of Facc's total 15000 bytes).

But the net is right - it was a mistake not to have command line options for
things like the number of buffers. To have a window or not have one. Etc.  I
thought about  this and about how disappointed I was that Facc's user inter-
face dominated the amount of space in Facc  to such  a large degree and then
also thought  about  how  I could provide a general solution. The answer was
quite simple:

Split Facc into the  two  functions it really is. 1) A Cache control system.
2) A user interface. A program called Facc still exists but it is only about
five kbytes and has no user interface. Instead it listens in on a pre-defin-
message port waiting for SOME program to control its activities. There's now
a program call Facction (Facc Action) which has a complete command  line i/f
as well as a complete windowed interface. 

If you're not interested in watching Facc do it's thing, don't have facction
running at all. Another  nice  point though, is that YOUR program could com-
municate with Facc. This comes for free the way Facc is now designed. I will
publish the complete communication protocol for your programming pleasure.

One thing I can say right now, with all the new features like automatic low
memory handling and block analysis influencing LRU behavior, I am wondering
if I can still effectively explain how the naive user will  use it all (:-)

Perry S Kivolowitz
ASDG Incorporated
(201) 563-0529

---
Someone please pass this note on to PLink with my thanks to Andry Rechmat.