Path: utzoo!censor!geac!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!pmafire!uudell!bigtex!texsun!newstop!sun!quintus!johnt
From: johnt@quintus.UUCP (John Grant)
Newsgroups: comp.sys.mac.system
Subject: Two Questions about System 7
Message-ID: <1492@quintus.UUCP>
Date: 25 Feb 91 19:50:27 GMT
Article-I.D.: quintus.1492
Reply-To: johnt@quintus.UUCP (John Grant)
Organization: Quintus Corporation
Lines: 18

i)	Is there some suitable way of dealing with temporary files ?  What
	I am looking for is some automated way of dealing with them so that
	should a program terminate in some unfortunate manner, you
	don't slowly consume all available disk space with dead temporary
	files. Users of Word, Fullwrite etc etc would appreciate this - the
	need for "helper" inits would then be avoided.
	Better would be a method whereby the temporary files would stay
	around during one reboot, so that the user might be able to
	recover any data from them before the files are deleted on the 
	next reboot.  It strikes me that this functionality would be easy
	and inexpensive to implement.

ii)	I have heard that an, albeit small, RAM cache cannot be disabled.  I 
	would like someone to explain why we are *forced* to use this in a
	synchronous I/O environment - this 32K (?) is probably already
	implemented in the drive controller as a track cache, so why
	duplicate this functionality - doesn't this also hurt the
	performance of those NUBUS SCSI controllers with all the RAM ?