Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Logical Communication Endpoint ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Logical Communication Endpoint identifies a platform-independent point of information exchange among Logical Nodes. | ||
| + | |||
| + | A Logical Communication Endpoint provides a logical boundary for communication. It identifies the exchange point, the participating Logical Nodes, the communication roles, the Logical Data Structure Definition governing the exchanged information, | ||
| + | |||
| + | A Logical Communication Endpoint remains distinct from the technology used to realize it. Implementation profiles realize Logical Communication Endpoints through selected mechanisms such as DDS Topics, REST resources, RPC methods, Protocol Buffers messages, message queues, event streams, file exchange, shared services, or other mechanisms. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Specialization of Communication Endpoint from Part 1, Section 7.6; generalised from communication endpoint and topic material in the original FX Demo Reference Architecture. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Logical Communication Endpoint is not a DDS Topic, REST resource, RPC method, message queue, file, database table, shared memory location, or deployment artifact. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A logical health-status endpoint carries health-status information from reporting Logical Nodes to a logical Health Monitoring Node without prescribing the implementation technology used for the exchange. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | [[dido: | ||