From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Annex E.5 System.RPC
Date: Mon, 2 Apr 2018 21:39:58 +0200
Date: 2018-04-02T21:39:58+02:00 [thread overview]
Message-ID: <p9u0uc$pca$1@gioia.aioe.org> (raw)
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
next reply other threads:[~2018-04-02 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 19:39 Dmitry A. Kazakov [this message]
2018-04-06 13:40 ` Annex E.5 System.RPC Marius Amado-Alves
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox