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=-1.3 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,348865ddb50d3a12 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-04 09:48:03 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!fr.usenet-edu.net!usenet-edu.net!enst!enst.fr!not-for-mail From: Toshitaka Kumano Newsgroups: comp.lang.ada Subject: Re: Glade :- he distributed Annex Date: Fri, 05 Apr 2002 02:48:49 +0900 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: References: <3cab031b@filemon.telecable.es> Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1017942482 65587 137.194.161.2 (4 Apr 2002 17:48:02 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Thu, 4 Apr 2002 17:48:02 +0000 (UTC) Return-Path: X-Mailer: Mozilla 4.78 [ja] (Win98; U) X-Accept-Language: en-US,en,ja Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:22110 Date: 2002-04-05T02:48:49+09:00 Hi, Pedro Menendez wrote: > are there any restrictions regarding the communication in a distributed > application. I mean clients and server/s on the same LAN and the such. As far as I understand, no restriction such as "same LAN", if you mean "same segment". And different segments could be linked by adding appropriate routing ? Glade just requires the TCP connection is stable, and, of course, unstable network, by such as a congested router or by ethernet with many collisions, could introduce some instability to a Glade application, if you don't consider some recovery mechanism in your design of the application. The distribution annex, a sophisticated RPC, is one thing, and the fault tolerance of transport layer underlying it is another matter. In other malicious words, I consider Glade by itself could not be used for practical, fault tolerant or real-time (deterministic response) application. This can be "restriction" in your application domain. > This is the case in MPI, isn't it? I don't think so. TCP/IP based MPI implementations don't have such restrictions. MPI, in its strict meaning, is just a standard (paper) of API and protocol of presentation/session layer, and the standard says nothing about its lower layer of implementation. So answer to your question is "it depends". For example, our proprietary implementation of MPI is directly on the link layer of our in-house bus, without TCP/IP protocol stack, aimed only for performance, without any routing capability. In this case, the applications can talk only if they are on "same bus". -- Toshitaka Kumano