🚀 go-pugleaf

Since we are talking Claris flames, I might as well burn this one that
has been brewing in my head for a few months now.

We are using FMPro on  a network and we use it to track the calls from
our clients -- we are a support organization. Anyway, in addition to
running FMPro to record the progress of problem resolution, we do other
things with our client Macs (weird things), like running 8 or more apps
at once. So anyway, there is this new feature in the Pro version where
it politely jams all the clients accessing the database if it loses
contact with one client. In addition, it puts a dialog up on the host
saying something like:
	The host has lost contact with <foo>. All activities will be
	suspended until contact is restablished or you may disconnect
	this client by pressing the Disconnect button.

There are problems with this in my book. I thought the whole point of
client-server applications was to create a system in which a resource
could be distributed among several clients and the clients should not
notice each other (or not notice each other to a great extent, as in
speed). WHY DOES ONE MACHINE CAUSE THE WHOLE SYSTEM TO LOSE?

I spoke to some engineer at Claris and he said that this was their
solution to the corrupted index problem of FMII.

Has anyone else had this problem? Could someone from Claris shed some
light on this, please?!?!?!


Many thanks,
Mike
--


=======================================================================
| Michael L Barrow    | "If any of the above offended you, it was     |
| <mlbarrow@mit.edu>  |  my idea to do it -- not MIT's"               |
|---------------------------------------------------------------------|
|     Consultant      | MIT Computing Support Services (CSS)          |
|     Member          | Student Information Processing Board (SIPB)   |
|     Student         | Computer Engineering Major, '93               |
=======================================================================