Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:r:rpc [2026/07/18 12:33] – external edit 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:r:rpc [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 9: / Line 9: @@
 An RPC interface typically presents interactions as named operations with input parameters, output results, errors, and invocation semantics. RPC implementations may use different protocols, data formats, service definitions, transport mechanisms, authentication mechanisms, and runtime frameworks.
-In the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], RPC references identify possible implementation mechanisms. RPC does not define the logical meaning of a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], data structure, policy decision, command, acknowledgement, release package, or runtime plane.
+In the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]], RPC references identify possible implementation mechanisms. RPC does not define the logical meaning of a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], data structure, policy decision, command, acknowledgement, release package, or runtime plane.
 An RPC interface can realize, expose, or support a logical communication pattern selected by an implementation profile. The logical architecture remains independent of RPC operation names, parameter formats, service definitions, transport protocols, framework selection, and deployment boundaries.