[11515] in Athena Bugs
Re: MacDiscuss performance issues....
daemon@ATHENA.MIT.EDU (Tim O'Malley)
Thu Dec 9 14:01:42 1993
Date: Thu, 9 Dec 1993 13:55:49 -0500
To: hoffmann@MIT.EDU
Cc: mlbarrow@MIT.EDU, bugs@MIT.EDU, blue-box@MIT.EDU, ij@MIT.EDU
In-Reply-To: Re: Re: MacDiscuss performance issues....
Reply-To: timo=reply@BBN.COM
From: Tim O'Malley <timo@BBN.COM>
hola.
hoffmann@mit.edu writes:
-> I imagine there could be a middle ground between the two
-> extremes...
Most editors and word processors solve this problem by giving the user
an option to save the file at any time -- simply choose "Save" from the
File menu.
Saving the meetings file seems to be a similar situation.
.........................................................................
. happy daze . .
. -tim O . Complex problems have .
. <timo@bbn.com> . simple, .
. Tim O'Malley . easy-to-understand, .
. BBN/DSI Engineering . wrong answers. .
. (617) 873-3076 . .
.........................................................................
hoffmann@mit.edu writes:
-> Date: Thu, 9 Dec 1993 09:08:19 -0500
-> From: mlbarrow@MIT.EDU
->
-> ... If this is true, it's unnecessary. Take as
-> an example the Macintosh NNTP client Newswatcher. I use this app and it
-> performs well under the same configuration. On startup, it reads in the
-> news file and keeps it memory-resident. When the user quits, it writes the
-> new news file. All modifications to the news file take place in memory,
-> resulting in better performance...
->
-> The primary drawback of a fully-cached newsgroup file or
-> discuss meetings file (as you describe it above) is that
-> if you die in the middle of your session (your machine I
-> mean) then you've lost ALL your state and are forced to
-> relive history.
->
-> I imagine there could be a middle ground between the two
-> extremes...
->
-> -Ron
