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,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,69d0699f9f49163 X-Google-Attributes: gid103376,public From: Laurent Pautet Subject: Re: Client/Server with Distributed Annex? Date: 1997/01/30 Message-ID: #1/1 X-Deja-AN: 213276109 sender: pautet@scapin.enst.fr references: <5cpebe$9ic$1@goanna.cs.rmit.edu.au> content-type: text/plain; charset=iso-8859-1 organization: Ecole Nationale Superieure des Telecommunications, Paris France mime-version: 1.0 newsgroups: comp.lang.ada Date: 1997-01-30T00:00:00+00:00 List-Id: >>>>> "Dale" == Dale Stanbrough writes: Dale> After looking at ACT's Glade, and the distributed systems annex, Dale> I became unsure of whether the DS annex would allow for Dale> client/server programs where clients come and go dynamically, Dale> but the server lives on. I got the feeling that it was all a bit Dale> too static for this to be the case. This feature has already been used by some companies to implement some kind of replication. Yes, the DS annex allows to restart clients even when some of them have died. It can use a mechanism based on RACWs, but other approaches with plain RPCs are also possible if the server doesn't need to notify or to keep tracks of its clients. Have a look at DSA/Examples/Eratho/dynamic. Partitions 2, 3 and 4 are in some way the clients you are talking about. We can add such example in GLADE release if people are interested in this kind of example. -- -- Laurent