====== 15.3 FX Communication Technology Independence ======
[[fxdemo:03-part:15-relationship-to-implementation-profiles-psm:start | Go To Relationship to Implementation Profiles / PSM ]]

The FX Demo Logical Profile does not prescribe a communication technology.

An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] selects communication mechanisms to realise FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]] and FX logical interaction patterns. Those mechanisms include, for example, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rest|REST]], [[dido:99_annexes:annex-b-terms-and-definitions:r:rpc|RPC]], Protocol Buffers-based services, message queues, event streams, file exchange, shared services, or other communication approaches.

The selected communication mechanism realises the FX logical endpoint. It does not redefine the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoint]], Communication Role, FX [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], or FX logical interaction pattern.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>