From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ffe7b9269a00c843 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1993-03-24 15:18:47 PST Newsgroups: comp.lang.ada Path: sparky!uunet!pipex!marble.uknet.ac.uk!mcsun!Germany.EU.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!agate!linus!linus.mitre.org!linus!mbunix!emery From: emery@dr_no.mitre.org (David Emery) Subject: Re: Complexity of "distributed" v "monolithic" (was Re: Ada cost breakpoints) In-Reply-To: matwood%peruvian.cs.utah.edu@cs.utah.edu's message of 22 Mar 93 20:13:35 MST Message-ID: Sender: news@linus.mitre.org (News Service) Nntp-Posting-Host: dr-no.mitre.org Organization: The Mitre Corp., Bedford, MA. References: <65260@mimsy.umd.edu> <1993Mar21.120121.16006@hellgate.utah.edu> <1993Mar22.201336.5850@hellgate.utah.edu> Date: Wed, 24 Mar 1993 22:30:55 GMT Date: 1993-03-24T22:30:55+00:00 List-Id: When designing distributed applications, consistency becomes more important and harder to achieve. If you have a pipe of three programs, for instance, with a common data stream, it's hard to make sure that a change to the data stream definition is adopted by all three programs. In our experience doing client/server in Ada, the Ada compiler and library system (that so many people complain about) is instrumental in keeping our distributed software in sync. dave