[comp.protocols.appletalk] MultiLauncher

falken@apple.com (Dave Falkenburg) (08/05/89)

In article <1145@mailrus.cc.umich.edu> dave@ronin.cc.umich.edu (Dave 
Koziol) writes:
> Tim W Smith <ts@cup.portal.com> writes:
> >What do you do if a person runs an application and then reaches around
> >behind the Mac and pulls out the LocalTalk connect for a couple of
> >minutes so that the server will think they died?  Does the DRVR do
> >something to discourage this?
>  
> What do you want me to do? How do you want me to detect this state?
>  
> No, if the user does this there's nothing I plan to do software wise.
> To discourage our users from doing it, we don't tell them how 
MultiLauncher
> works.  Besides, if they manage to check out an application, they 
generally
> don't care if anyone else can.  It doesn't help them to yank their 
> LocalTalk connection.  (We also have monitors at our sites who would (if 
they
> saw it), strongly discourage this sort of thing...)
>  
>  Dave Koziol             | Internet: koziol@um.cc.umich.edu 
>  Computing Center        | Bitnet:   UserDave@umichum.bitnet          
>  University of Michigan  | UUCP:     ...!umix!um.cc.umich.edu!koziol 
>                          | GEnie:    D.KOZIOL1
>  ------------------------------------------------------------------------
-
>  Disclaimer:   "They don't pay me enough to need a disclaimer"



Gee Dave, aren't you running the software off of the appleshare server 
too??   If you pull out the network, then you also lose the server-- 
the same net effect as pulling a diskette out of the drive when you are
running a program off of it (well not EXACTLY-- with a disk you can always
cleanly re-insert it and the mac will recover)

If MultiLauncher is designed for running software off an AFPServer, you 
don't need to worry about the case where the user unplugs the network.

Actually, it's pretty easy to check if the user has disconnected the 
network-- periodically look for the server-- if you cant find it, you
have to panic, right???  There are a few other more important problems
like "what if the server is down before you run anything?"  "what happens
if the net 'hiccups' for a few seconds", "what if your machine crashes",
etc. etc. etc.

I guess if you are running software off a server, you're screwed if the 
net goes down anyway...

Also, if i'm not mistaken, MultiLauncher works via ATP, not ASP--  using
ASP would make life a little easier for a programmer by handling timeouts, etc.

-dave falkenburg

disclaimer: this is ME talking, not Apple