Problem with Scratch Directory

[Vadim S. Kaplunovsky]

> Same problem here with the scratch directory (/tmp/OmniWeb).
> Although the behaviour can be changed by selecting a
> different directory in the Preferences Menu, it is not a good
> thing to have to do that for each user (for example, we have
> here a "/zap" directory in each machine that is meant for
> temporary file storage and gets erased when the local user
> logs out). Either store things in tmp directly (a mess, I
> have ot admit), change the permissions so that it is erasable
> by all other users or erase it when the app exits (I know, I
> know, what happen when OW crashes?). Otherwise the result is
> that suddenly a user can get no images downloaded... 

> 

Unfortunately, neither /tmp/OmniWeb nor any of the above suggestions would work  
for several users trying to use OmniWeb at the same time on NeXTs that are  
networked together and share their filesystems.  A much better way is to create  
a separate scratch directory for each instance of the OmniWeb.app running, for  
example /tmp/OmniWeb$$  --- this way, different users would never get in each  
other's way.  Alternatively,  OmniWeb may use $HOME/.OmniWeb-tmp --- this may  
give trouble to users trying to run two instances of OmniWeb.app under the same  
userid, but it in case of OmniWeb crash, it would get the scratch files cleaned  
up whenever OmniWeb.app manages to quit normally.
> 

> By the way, great work!!
> -- Fernando
> 

-- Vadim.
*****************************************************************************
Vadim S. Kaplunovsky,              | vadim at bolvan.ph.utexas.edu (NextMail OK)
Assistant Professor of Physics,    | #include <std_disclaimer.h>
University of Texas at Austin.     | #excuse bad_typing.