This is tres neato.  A nice, simple improvement, IMHO, would be to have
more than one level of severity:

	1. Discard completely unneeded things.

	2. Discard things that are unneeded, but expensive to recompute.

	3. Discard things that are irreplacable.  Unfortunate, but probably
better than letting the image just quit.


"Space hogs" would register with one of these levels, and the low-space
code would try less-severe hogs before moving to more severe ones.

Food for headaches: how do you extend this kind of scheme to handle
other resources, such as file handles and sockets?

	-Lex




Georg Gollmann <georg.gollmann at tuwien.ac.at> wrote:
> --============_-1257709381==_============
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
> 
> The current LowSpaceWatcher just alerts the user. This is not useful 
> for servers or for situations when objects are cached and should be 
> discarded when space becomes tight. I have now generalized the 
> mechanism used in my MailArchiver 
> (http://macos.tuwien.ac.at/Squeak/mailArchiver.html).