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.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Annex E.5 System.RPC
Date: Mon, 2 Apr 2018 21:39:58 +0200
Organization: Aioe.org NNTP Server
Message-ID: <p9u0uc$pca$1@gioia.aioe.org>
NNTP-Posting-Host: kQkuQcRDy1QFvWpyB1foYw.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
X-Mozilla-News-Host: news://news.aioe.org:119
Content-Language: en-US
X-Notice: Filtered by postfilter v. 0.8.3
Xref: reader02.eternal-september.org comp.lang.ada:51301
Date: 2018-04-02T21:39:58+02:00
List-Id: <comp.lang.ada>

1. Why the name is fixed "System.RPC" instead of being specified in by a 
representation clause, e.g. in order to have multiple independent 
implementations/transports?

2. It seems that the design of Do_RPC and Do_APC interface requires all 
parameters stored in Params_Stream_Type. The contents is copied to the 
transport. This is one unnecessary copying when the transport has a 
stream interface, and also a restriction to have memory ready to keep 
all parameters and results cached. The transport cannot establish a 
channel to the callee because Do_RPC/APC are called *after" writing the 
stream, when the callee is yet unknown. Was it considered *first* 
initiate RPC/APC and *then* serialize the parameters?

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de