Article View: comp.sys.mac.apps
Article #7704Re: Filemaker Pro stupidity
From: Brian Schipper
Date: Mon, 11 Mar 1991 18:19
Date: Mon, 11 Mar 1991 18:19
19 lines
1405 bytes
1405 bytes
mlbarrow@athena.mit.edu (Michael L Barrow) writes: >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? Actually this is a "feature" that was inherited from FileMaker II. The host notifies clients periodically of changes in the database. When one of the clients is busy, it can cause a lockup for everyone. What we added for FM Pro is the alert that lets you know this is happening. As you pointed out, this is not an ideal solution, but it is an improvement over FileMaker II, since it does alert you to the source of the problem. Hopefully we'll be able to do better in a future release. Brian -- Internet: skip@claris.com AppleLink: SCHIPPER1
Technical Details
Message-ID:
<211@claris.com>Path:
arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!claris!skipReferences:
<92710@lll-winken.LLNL.GOV> <200@claris.com> <MLBARROW.91Mar8190432@heath-bar-crunch.mit.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!claris!skip From: skip@claris.com (Brian Schipper) Newsgroups: comp.sys.mac.apps Subject: Re: Filemaker Pro stupidity Message-ID: <211@claris.com> Date: 11 Mar 91 18:19:32 GMT References: <92710@lll-winken.LLNL.GOV> <200@claris.com> <MLBARROW.91Mar8190432@heath-bar-crunch.mit.edu> Organization: Claris Corporation, Santa Clara CA Lines: 19