Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!usc!apple!agate!shelby!csli!dmr
From: dmr@csli.Stanford.EDU (Daniel M. Rosenberg)
Newsgroups: comp.sys.mac
Subject: Re^2: What I'd like to see in the AppleShare of the 90's
Message-ID: <11724@csli.Stanford.EDU>
Date: 15 Jan 90 03:08:47 GMT
References: <25184@brunix.UUCP> <25862@cup.portal.com> <25447@brunix.UUCP> <25942@cup.portal.com>
Sender: dmr@csli.Stanford.EDU (Daniel M. Rosenberg)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 26

MacUserLabs@cup.portal.com (Stephan - Somogyi) writes:

>If you kick out the LocalTalk connector on your Mac, you lose network
>services, but your Mac *should not* crash. At least, the AShare client
>software shouldn't cause that crash, it should be giving you the "the
>server disappeared" dialog.

Right now, if I kick out the LocalTalk connector to my Mac, nothing
happens. (I did it right after the comma.) I can do it for a pretty long
period of time, too -- I did it right after those parentheses and
went down the hall for a drink of water.

I am typing this in a window across AppleTalk onto my UNIX machine,
by the way.

When the *server* goes down, however, it crashes immediately, no chance
for recovery. I am not sure that anything really *can* happen at that
point -- if that Mac has failed, your work is lost, as if your Mac
had failed. Isn't that true? Nice programs will let you recover what you're
working on, of course....

Dan

-- 
# Daniel M. Rosenberg     //  Stanford CSLI  // Eat my opinions, not Stanford's.
# dmr@csli.stanford.edu  // decwrl!csli!dmr // dmr%csli@stanford.bitnet