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,59003dcff2152233
X-Google-Attributes: gid103376,public
From: pautet@email.enst.fr (Laurent Pautet)
Subject: Re: More on Distributed Systems Annex
Date: 1996/09/13
Message-ID: <51c0c4$4av@scapin.enst.fr>#1/1
X-Deja-AN: 180396604
sender: pautet@scapin.enst.fr
references: <3238706F.96B@joy.ericsson.se>
content-type: text/plain; charset=iso-8859-1
organization: Ecole Nationale Superieure des Telecommunications
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-09-13T00:00:00+00:00
List-Id: <comp.lang.ada>


Jonas Nygren  <jonas@joy.ericsson.se> wrote:
>
> Can I use the DSA features to write a client-server solution the 
> same way as I could with e.g. RPC. When I look at the examples in the
> Rational it seems as if I need a unique executable for each client 
> (partition). This would mean I could not invoke two instances of the
> same client executable because I would then have two partitions with 
> the same ID executing at the same time.

Have a look at DSA's example RACW. Part2 and Part3 are identical with
a duplicated normal package. But they don't have the same partition
id. Each partition derives a given abstract type which is also
different and use this type to build distributed objects - RACW (or if
you prefer, reference to themself). But, what you can not write is a
client / server application with twice the same RCI.

-- 
-- Laurent