Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!lll-tis!ames!sdcsvax!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Low Memory Server From ASDG
Message-ID: <8706120713.AA08259@cogsci.berkeley.edu>
Date: Fri, 12-Jun-87 03:13:42 EDT
Article-I.D.: cogsci.8706120713.AA08259
Posted: Fri Jun 12 03:13:42 1987
Date-Received: Sat, 20-Jun-87 13:48:03 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 42
Keywords: publicly redistributable shared library


> As part of the development of FacII - I have written a general purpose
> low-memory ``server.'' That is,  an  agent  which will allow arbitrary
> processes to register  with  it  their  desire to be notified when the
> system is low on memory (actually - whenever an AllocMem fails).

!!!PLEASE include a priority!!!  Some users of this function will want to dump
their memory at the earliest hint of need.  Others will want to be stingy
and hang on until there is no alternative. 

With the distibution list suggested priorities for different things.  Not
an exact science, but a guide at least.

!!!PLEASE!!!
----------------------------
Also, if possible, pass the ammount of memory needed.
----------------------------

FaccIII ideas:

2> If it is not already planned, give the control window the ability to
   "disappear".  Not just hide, but go away completly.  Sort of like a TSR,
   terminate and stay resident.  If the user wanted the window again they
   could crank up the icon and FaccIII would be smart enough to
   link up the the public port it left last time.

1> When a large file is loaded in as a chunk it is unlikely that it will be
   accessed again soon.  Think about a large binary like an assembler, text
   editor or "DeluxeMusic".  Any buffers used to hold these are almost
   completly wasted.

   The exception here is the portions of the file used for overlays and the
   blocks of type "T.LIST".  Blocks of type "T.SHORT" are also of a much
   higher priority than simple data blocks of a large file.

   I realize that this gets into mucking with the structure of a disk of type
   "DOS ". 
   -> This would only be acceptable if you checked the type of disk
   you are buffering and fell back to the old way on types like "FDOS" or
   "DOS2". <-

Have an nice day!