Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!husc6!harvard!spdcc!m2c!ulowell!page
From: page@ulowell.cs.ulowell.edu (Bob Page)
Newsgroups: comp.sys.amiga
Subject: Re: AutoFacc (binary and doc)
Message-ID: <1400@ulowell.cs.ulowell.edu>
Date: Thu, 18-Jun-87 12:15:58 EDT
Article-I.D.: ulowell.1400
Posted: Thu Jun 18 12:15:58 1987
Date-Received: Sun, 21-Jun-87 13:30:26 EDT
References: <8580@amdahl.amdahl.com> <3320@well.UUCP>
Reply-To: page@ulowell.cs.ulowell.edu (Bob Page)
Organization: University of Lowell
Lines: 26
Keywords: facc autofacc shrink add delete buffers cli executable ASDG daemon

perry@well.UUCP (Perry S. Kivolowitz) wrote:
>... Facc ... listens in on a pre-defined message port ...
>... Facction ... has a complete command line i/f ...

Very nice.  May I suggest you go further (if you have not already done so):
Keep 'Facc' the user interface, and have something like 'FaccD' (Facc Daemon)
grab messages/requests.  Also have Facc start up FaccD if it isn't already
running, so all this is transparent to the user, after you tell her to
initially install FaccD in LIBS: or something.

Your idea is really the way to go for ANY Amiga program which does its
thing continuously, like PopCLI, MemWatch, FunKeys, FastFonts, etc...
Have a front end that's 5K or so and does all the command line parsing
and intuition/menu/graphics stuff, then pass a message to a daemon that
is only 1200 bytes or whatever.  That way all your parse code isn't
still hanging around for the life of the program.

I am currently working on two daemons along this principle, both for
the public domain -- I suppose I can post my interface code, and we
can use it as a 'stanard template' for parsing/daemon-starting/messaging
since I have no monetary considerations at stake.  Would it be useful to
the Amiga community at large?

..Bob
-- 
Bob Page, U of Lowell CS Dept.   page@ulowell.{uucp,edu,csnet}